MCP servers | AskElephant | API Documentation

AskElephant exposes two remote MCP servers:

Server	URL	Use it for
AskElephant	`https://app.askelephant.ai/mcp`	Giving your agent access to AskElephant workspace data such as meetings, transcripts, and customer context.
AskElephant API Docs	`https://docs.askelephant.ai/_mcp/server`	Giving your agent the AskElephant public API docs and schema context while building integrations.

Which one should I install?

Install AskElephant if you want your agent to work with live AskElephant data.

Install AskElephant API Docs if you want your agent to help write code against the AskElephant public API.

Install both if you want an agent that can:

Look up customer meetings and transcripts
Explain the public API surface
Draft integration code using the current API docs

Recommended names

Use these names when the client lets you choose a display name:

AskElephant
AskElephant API Docs

Authentication and access

The AskElephant MCP server acts as the user who connects it. MCP tools require the corresponding resource scopes and remain subject to the user’s current AskElephant role, privacy rules, and other workspace permissions.

OAuth is the recommended connection method. Identity scopes establish the connected user. If the token includes resource scopes, those scopes limit which tools can run. Identity-only OAuth connections, including existing Claude and ChatGPT connectors, continue to act as the connected user and do not need to be reconnected. New dynamic registrations that omit a scope list allow the resource scopes advertised for MCP; the authorization and consent screens still determine what a newly issued token receives. Administratively registered clients that request resource scopes remain limited to those scopes.
API keys are also supported for clients that send an x-api-key header. MCP acts as the user who created the key.
Resource scopes selected for an API key or OAuth app limit both Public API requests and MCP tools. Update the key’s scopes or rotate it if the client needs additional tools.
Tools that return several resource types require each resource’s read scope. For example, company or contact expansions that return engagements also require engagement and user scopes.
API keys need engagements:private:read or engagements:private:write to read or modify private engagement data. Without the private read scope, private meetings are omitted from list and compound results.
Workflow creation and decomposition require workflows:write. Expert-rule reads and mutations require expert_rules:read and expert_rules:write; engagement scopes do not grant these capabilities.
Removing a user’s access or revoking the OAuth connection or API key removes the corresponding MCP access.

Connect MCP with a user account that has only the access the agent needs. Do not share an API key between users.

REST vs MCP visibility

Do not use MCP access as a mental model for REST workspace credentials. MCP tools act as the connected user and honor that user’s in-app permissions, privacy rules, and workspace role. The Public API follows separate workspace engagement visibility rules for workspace-scoped credentials.

Platform guides

Practical notes

Both URLs are remote MCP servers. You do not need to run a local bridge process.
If your client prompts you to sign in or authorize access, complete that flow before testing.
UI labels change frequently across these products. The pages in this section describe the current setup pattern, but a nearby label like Apps, Connectors, or Custom connector may vary by plan and product version.