MCP

Aepto exposes one remote Model Context Protocol server over Streamable HTTP. End users installing Claude should start on the product guide: Claude connector. This page is for integrators and hosts.

https://app.aepto.com/mcp

Use exactly that URL — no trailing slash. Directory listing, custom connector, and plugin all use this endpoint; there is no second server.

Connect Claude (official connector)

Recommended for most people — full steps on Apps → Claude connector. Direct listing (Claude login required): claude.ai/customize/connectors/id/aepto.

While signed in to Claude, open claude.ai/customize/connectors/id/aepto — or Customize → Connectors → search Aepto.
Choose Connect / Install.
Complete Sign in with Aepto. The consent screen should show Aepto (not “Unknown App”).
After approval, tools named aepto_* appear in the session. Catalog: MCP tools.

On Team / Enterprise plans, an Owner (or someone with library permission) enables the connector for the organization under Organization settings → Connectors; each member then connects with their own Aepto account. Members without permission may see Request instead of Connect.

Connect Claude (custom connector)

Use this if you prefer to paste the URL yourself, or the directory entry is not available on your plan.

In Claude, add a custom connector / remote MCP server (web).
Name it (e.g. Aepto) and paste https://app.aepto.com/mcp as the server URL.
Complete Sign in with Aepto when prompted. Prefer Claude’s published OAuth identity when asked.
After approval, the same aepto_* tools appear. Catalog: MCP tools.

Team / Enterprise Owners add custom connectors under Organization settings → Connectors; members then Connect individually.

Claude plugin

If you install the Aepto Claude plugin bundle, its .mcp.json still points at https://app.aepto.com/mcp. Skills teach when to use the tools; they do not add a second backend.

API key auth (other hosts)

Hosts that support a custom Authorization header (Cursor, scripts, etc.) can send:

Authorization: Bearer aep_live_...

Create the key at app.aepto.com/api-keys with scopes that cover the tools you need. Claude’s official and custom connectors normally use Connect OAuth instead of pasting a key.

OAuth discovery (for hosts)

Protected resource metadata: https://app.aepto.com/.well-known/oauth-protected-resource
Authorization server metadata: https://app.aepto.com/.well-known/oauth-authorization-server
Authorize / token / revoke: https://app.aepto.com/connect/authorize, https://app.aepto.com/connect/token, https://app.aepto.com/connect/revoke

Details: Connect. Claude’s redirect URI must match the registered value (https://claude.ai/api/mcp/auth_callback).

FAQ

Is Aepto in Claude’s official Connectors Directory?

Yes. While signed in to Claude, open claude.ai/customize/connectors/id/aepto, or search Aepto under Customize → Connectors. Same MCP URL as a custom connector.

What is the exact MCP URL?

https://app.aepto.com/mcp with no trailing slash. Required for custom connectors and other Streamable HTTP hosts; the directory listing uses this same endpoint.

Do I need an API key for Claude?

Usually no. The official connector and custom connectors complete Sign in with Aepto (Connect OAuth). Hosts that support a custom header can instead send Authorization: Bearer aep_live_....

Where is the tool list?

See MCP tools for the aepto_* catalog. Live source of truth is tools/list on the MCP URL.

Consent shows “Unknown App” — is that wrong?

The consent screen should show Aepto. If it does not, confirm you used the official Aepto connector or the exact MCP URL above, and check OAuth notes under Connect.

Product FAQ hub: FAQ.