Troubleshooting MCP

Resolve common Creator Eagle MCP connection, authentication, and background-job errors.

No Creator Eagle API key reached the server. Confirm that CREATOR_EAGLE_MCP_API_KEY exists in the client process and that the client sends it as Authorization: Bearer ....

Some clients do not interpolate environment variables inside JSON headers. Use the client's environment-backed bearer-token option when available.

`401 Unauthorized`

The credential is missing, invalid, expired, or revoked. OAuth clients should reconnect and complete sign-in again. API-key clients should create or select a valid ce_... key with mcp:use.

For an API key, verify that it includes mcp:use and belongs to an active Creator Eagle workspace. For browser OAuth, verify the account can sign in to Creator Eagle through WorkOS AuthKit and that the MCP WorkOS application allows the Worker's exact /callback URL.

A background tool returns `running`

Keep calling poll-task with the same Trigger runId. Do not restart the original tool or substitute a NanoInfluencer jobId for a Trigger runId.

For similar search specifically, call poll-similar-creator-search with the provider jobId. If that call returns a Trigger runId, use only poll-task from then on.

Contact matching fails

The creator must already be in an influencer list. Add or favorite the creator first, then call find-creator-contact again.

The tool list is missing or stale

Restart the client or begin a fresh MCP session. Confirm the configured URL is exactly https://mcp.trycreatoreagle.com/mcp, then ask the client to list tools again.

The workflow prompts do not appear

MCP prompts are a client-controlled capability. Some clients and MCP aggregators expose tools but do not provide a prompt picker or forward prompts/list and prompts/get. This does not disable Creator Eagle tools. Follow Workflow prompts manually, and rely on the server instructions and tool descriptions for call-specific safety rules.

A YouTube enrichment takes a long time

Channel enrichment summarizes multiple videos and commonly takes one to three minutes. Use fewer videos per channel for a quicker first pass, and continue polling the returned runId rather than starting duplicate runs.