Integrate

Model Context Protocol

Connect Muse, ChatGPT, Claude, Codex, Cursor, and VS Code to Endurance HQ. Public event information is available without an account. Organizer tools use your delegated permissions and check your Endurance HQ access on every operation.

Remote endpoint

https://api.endurancehq.app/mcp

Connect an assistant

Muse

Official setup guide

Open Muse and paste the custom connector prompt below.
Review the setup Muse proposes, then run the public-data check before granting account access.

Custom connector prompt

Create a custom connector for Endurance HQ. Read https://www.endurancehq.app/developers/mcp and connect to its Streamable HTTP MCP server at https://api.endurancehq.app/mcp. First list its public tools and run this read-only check: Use ehq_platform_overview to explain what Endurance HQ does and which information is public. Do not create or change anything. Before accessing my account, guide me through the supported authorization flow. Do not ask me to paste a password or token into chat. Ask before making any changes.

Custom connectors are not reviewed by Meta. This setup does not install a reviewed directory listing; availability and account authorization must be verified in Muse.

About Muse directory review

Verify the connection

Public-data check

Use ehq_platform_overview to explain what Endurance HQ does and which information is public. Do not create or change anything.

Account access check

Use ehq_events_list to list the events I can access. If account access is missing, help me authenticate. Do not create or change anything.

Public tools work without an account. Personal tools require account authorization and the appropriate permissions. If only public tools appear, authenticate in your assistant and refresh the tool list. Approving a connection does not confirm that an action succeeded; check the returned result and your account.

API key alternative for Codex

For a machine workflow, create a scoped API key in Endurance HQ and provide it through the EHQ_API_KEY environment variable. Use this configuration instead of the OAuth connection, and keep the key out of source files and chat.

[mcp_servers.endurance-hq]
url = "https://api.endurancehq.app/mcp"
bearer_token_env_var = "EHQ_API_KEY"

Public tools

Without a credential the endpoint serves two read-only tools: ehq_platform_overview (what Endurance HQ is, who it is for, and how to integrate; the same content as /llms.txt) and ehq_public_event (the published facts of a race website hosted on Endurance HQ, by host or event slug: dates, distances, prices, registration status, pages, FAQ, schedule). Every other tool appears once the client authenticates.

curl -X POST https://api.endurancehq.app/mcp \
  -H 'content-type: application/json' -H 'accept: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"ehq_public_event","arguments":{"host":"hardrock.endurancehq.app"}}}'

Task references

Agents can pass a short reference such as EHQ-184 to ehq_tasks_get, ehq_tasks_update, or ehq_tasks_comment. The same permission checks apply as when opening the Task in Endurance HQ.

Knowledge setup

ehq_knowledge_setup_status reports what feeds a workspace's organizational knowledge and what is left. Steps that need a credential, such as a Granola API key or mailbox consent, come back as a link that opens that form in Endurance HQ; no tool accepts a credential. ehq_knowledge_granola_sync_propose and ehq_knowledge_backfill_propose prepare plans the user approves in Endurance HQ, like ehq_changes_propose.

Discovery

The endpoint implements Streamable HTTP, stateless compatibility for older clients, and RFC 9728 protected-resource discovery. Schedule and Task writes use the same canonical services as the Endurance HQ dashboard and Cairn.