
Loops Mcp
io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.1Updated Oct 24, 2026
MCP server for Loops: contacts, events. Needs a free API key.
Overview
A local MCP server that connects an assistant to Loops, letting it work with contacts and events through the Loops API.
- What you can do
- Manage contacts in Loops, such as creating or updating contact records and their details, through the Loops API. Work with events, such as sending or listing event data associated with contacts. The manifest lists no individual tools, so the exact set of operations is not documented here.
- When to use it
- Useful when you want an assistant to handle Loops contacts and events directly, for example keeping contact records current or recording events, instead of switching to the Loops interface.
- Requirements
- Runs as a local process on the user's machine, installed from the npm package @mrfentmen/loops-mcp over stdio, so a Node.js runtime is needed. A free Loops API key is required; the manifest declares no environment variables or headers, so how the key is supplied is not specified. Network access to the Loops API is needed.
Installation
In SourceWeft
- Open Loops Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
2- v1.0.1LatestOct 17, 2026
- v1.0.0Sep 22, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.