Create an API Key and Connect an AI Assistant
Create a scoped FoxCue API key in Settings → Developers, copy the API base URL, manage hosted OAuth connections and configure a local MCP client.
Settings → Developers is where you connect apps and AI assistants to FoxCue. Workspace owners create scoped API keys there, copy the API base URL, browse the API documentation, and manage hosted OAuth connections or copy the local MCP configuration.
Only workspace owners can create, view and revoke API keys.

Create API key, with a name, an expiry and permission scopes.
Create an API key
Open Developers
Go to Settings → Developers and click Create Key.
Name the key
Enter a Key Name. Use a separate key for each integration so you can revoke it on its own.
Choose Expires After
30 Days, 90 Days or 1 Year.
Choose Permissions
Select only the permissions the integration needs. See Authentication and scopes.
Save your key
Click Create Key. Save your API key shows the full key once. Click Copy key and store it in your integration's secret settings before you close the dialog. If you lose it, revoke the key and create another.
Workspace API keys are separate from AI provider keys (OpenAI, Anthropic, ElevenLabs). Removing an owner, or resetting their sign-in credentials, also invalidates the keys they created.
Revoke a key
In API Keys, click Revoke Key and confirm. Keys show Active, Expired or Revoked, with their last use.
API connection
API connection shows the API base URL for your workspace. Download OpenAPI saves the schema. The live schema lists 23 scopes, including library:read, library:write, publishing:read, publishing:write and publishing:publish. A hosted MCP connection requests 13 of those scopes. See the API reference and Authentication and scopes.

The MCP connection settings on Developers.
Connect an assistant (MCP)
Connect an Assistant provides two connection methods:
- OAuth Connection shows the hosted MCP endpoint,
https://app.foxcue.com/mcp, and its issuer. A compatible assistant signs in through FoxCue and requests scoped access to one owner workspace. This path does not require a manually created API key. - MCP client configuration starts a local stdio server from a FoxCue build on your computer. Put a scoped workspace API key in the client's private settings. The copied local configuration uses the broader workflow profile; the hosted connector uses the focused directory profile.
Owners can review saved OAuth grants under Authorized MCP Connections and use Revoke Access to invalidate a grant. The displayed status describes authorization, not whether a client is online. Revocation does not delete completed results or undo provider calls already sent.
See Connect an AI assistant with MCP for setup and OAuth permissions and troubleshooting for the 13 hosted scopes, expiry and revocation. A grant approved before brands:write and performance:write were requested does not gain them until you revoke it and connect again.
Frequently asked questions
Can members create API keys?
No. Only workspace owners can create, view and revoke keys.
Can an API key spend money?
Keys with generation:write can start AI generation and renders, which may incur provider costs. Grant it only when needed.