animawake docs

Connect

Connect claude.ai

Add an entity to Claude on the web as a custom connector with OAuth.

Claude on the web (claude.ai) connects to remote MCP servers as custom connectors. It registers itself with Animawake automatically, so you only need the server URL.

#Before you start

  • Custom connectors depend on your Claude plan. On Team and Enterprise plans, an owner adds connectors for the organization in the admin settings; members then connect their own account.
  • Create an entity in the portal. See the Quickstart.
  • Open the entity's Connect page and select the Claude.ai tab to copy the server URL:
Text
https://mcp.animawake.com/e/<workspace-slug>/<entity-slug>/

#Add the connector

  1. On claude.ai, open Settings and go to Connectors.
  2. Choose Add custom connector.
  3. Enter a name, for example the entity's name, and paste the server URL. Leave the advanced OAuth fields empty.
  4. Click Add, then Connect.
  5. Sign in to Animawake if asked, then click Allow Access on the Authorize Claude page.

To use the entity in a conversation, enable the connector from the tools menu in the chat input.

If automatic registration fails, you can use the same pre-registered credentials as Claude Desktop: generate them on the Claude Desktop tab of the Connect page and paste them into the connector's advanced settings. See Connect Claude Desktop.

#Check the connection

Start a new chat with the connector enabled and ask:

Text
Use get_startup to load your context. Who are you, and what did we do last time?

#Good to know

  • Connectors you add on claude.ai are tied to your Claude account. Depending on your plan and app version, they can also appear in the Claude desktop and mobile apps.
  • The access token lasts 30 days. When it expires, reconnect from Settings > Connectors.
  • Revoke access from the entity's Connect page. See Access tokens and keys.
  • For long projects, add a line to your Claude project instructions such as "At the start of each chat, call get_startup. Before we finish, call record_session." The entity then wakes and saves without being asked.

For problems, see Connection troubleshooting.