Connect an MCP Client

Use this guide to connect a remote MCP client to EnderDash. The client uses your account access when it calls EnderDash tools.

Before you begin

• Sign in to an EnderDash account that belongs to the organization you want to use.
• Use an MCP client that supports remote HTTP servers and OAuth sign-in.
• For automatic client registration, use a client that supports dynamic client registration.

EnderDash uses MCP protocol version 2026-07-28. The server URL is https://app.enderdash.com/api/mcp.

Connect your client

1. Add https://app.enderdash.com/api/mcp as a remote MCP server in your client.
2. Complete the EnderDash sign-in page that opens in your browser.
3. Approve read access when EnderDash asks for consent. This grants the mcp:read scope.
4. Ask your client to call list_organizations.
5. Choose the organization ID from the result for later tool calls.

You can also copy the organization ID from the Alerts or Knowledge Base page in the dashboard. Each organization tool takes an organizationId.

Read alerts and knowledge pages

Try these requests in your client:

• “List active alerts for organization <organization-id>.”
• “Show the context for alert <alert-id> in organization <organization-id>.”
• “Search the knowledge base in organization <organization-id> for backup failures.”

The client can use list_alerts, get_alert_context, and search_knowledge_pages for these requests. Use get_knowledge_page to read a full page. Long pages support offset and length.

The server checks your current organization membership and server access on each call. Owners and admins can also read delivery history, routing policies, and organization activity.

Edit a knowledge page

Your client must request mcp:knowledge:write in addition to mcp:read. Approve the new scope in the consent screen. The write tools then appear in the client's tool list.

For an existing page:

1. Call get_knowledge_page and read its current page or draft version.
2. Call update_knowledge_draft with that version and the new title or Markdown.
3. Call save_knowledge_draft with the draft version returned by the update.
4. Ask an organization owner or admin to call publish_knowledge_page if the page is not public yet.

Use create_knowledge_page to start a new unpublished page. If someone changes a draft after you read it, read the page again before you retry.

Review or remove a connection

Open Account → Security → Connected Applications in EnderDash. Review the scopes granted to each client. Remove a client's consent when you no longer want it to access your account.

For every tool, input, and access rule, see the MCP Server reference. Account OAuth explains the sign-in flow.

If the connection fails

• If sign-in does not start, check that the client supports OAuth for remote MCP servers.
• If automatic registration fails, check that the client supports dynamic client registration.
• If an organization is missing, check your membership in that organization.
• If a write tool is missing, request and approve mcp:knowledge:write.
• If a draft update reports a version conflict, read the page again before you edit it.