MCP docs

Connection URL

Paste this URL into a client that supports remote MCP:

Authentication

The client starts OAuth in the browser. Sign in and approve access to the Relin workspace before the agent can inspect workspace data.

1. Add the connection URL in your MCP client.
2. Start the authorization flow from the client.
3. Sign in to Relin.
4. Choose the Relin workspace the agent should access.
5. Return to the client after approval.

What agents can do

• List sources, destinations, recent events, delivery attempts, retry jobs, and open issues.
• Inspect metrics and delivery health when investigating failures.
• Create sources, destinations, and alert channels when you ask it to configure a workflow.
• Start replay for failed or filtered events after you approve the action.

Good agent tasks

• "Find why customer_123 did not receive invoice.paid."
• "Show failed deliveries for Production Stripe in the last hour."
• "Create a webhook destination for this test endpoint."
• "Replay the failed events after I fixed the receiver."
• "Summarize open webhook issues before standup."

Discovery

Clients that support server discovery can read the server card and OAuth metadata from these URLs:

Access control

Agent access follows the signed-in account and workspace membership. Remove workspace members when access should end.

Use the same judgment you would use for a human operator: agents can inspect operational data and can start actions when you ask them to. Review replay and configuration changes before approving broad or high-impact work.

Troubleshooting

• If the client cannot connect, confirm it supports remote MCP over HTTP.
• If authorization loops, sign out of Relin in the browser and start the client flow again.
• If the agent cannot see a source or destination, confirm your signed-in account belongs to the right workspace.
• If a replay request looks too broad, ask the agent to narrow by source, event, recipient, or time window before approving it.