Loops is a customer-engagement platform for lifecycle email and contact messaging. Its hosted MCP server uses OAuth, which should be authorized only against a dedicated test audience at first.
This guide prepares Loops for an MCP client. Dome's current agent-template connection schema does not yet support Loops' required CIMD client identification, so do not deploy the Loops agent template for OAuth until that support is available.
Choose a connection method
Loops documents OAuth for its hosted MCP server at https://mcp.loops.so. It uses Client ID Metadata Documents (CIMD), so the MCP client must support OAuth with CIMD; Loops does not ask you to create a client ID or client secret. See the Loops MCP guide.
Recommended: OAuth with a test audience
Create a test contact segment and one or two known test addresses before authorizing the connection. Do not connect a client that can send to real subscribers for the initial test.
- Add
https://mcp.loops.soas a remote Streamable HTTP MCP server. - Complete the browser sign-in and consent flow for the intended Loops account.
- Restrict the client or gateway to the approved discovery tools; Loops' upstream server can also create contacts, change lists, trigger workflows, and send email.
- Read a known test contact and verify that no campaign or transactional email is sent under the initial setup.
API-key note
Loops' hosted MCP documentation currently describes OAuth and does not document a static API-key authentication path for https://mcp.loops.so. Do not treat an API key for the general Loops API as a supported substitute unless Loops confirms that path for the hosted MCP server.
Verify Loops MCP
Use this checklist to confirm the MCP server is connected with the intended access.
- Connect the MCP client using the newly created authorization.
- Confirm that Loops MCP tools are discovered.
- Read one known test resource that the authorized identity is allowed to access.
- Attempt to read a resource outside the approved Loops boundary; it should be unavailable or denied.
- Confirm that no write capability beyond the reviewed setup is available.
Troubleshooting
If the server cannot find a contact, verify the test account, environment, and contact email first. Rotate a key immediately if it reaches source control or a prompt transcript.
Next steps
Use a CIMD-capable MCP client for Loops today. Publish a Dome Loops template only after its connection schema supports CIMD; do not replace Loops' OAuth flow with a general Loops API key.
