Connect
Sign in with your Abliteration account and choose an organization. No API key is required.- Codex
- Claude Code
- Claude
- Cursor
/mcp in the Codex CLI to check the connection.Try it
Tools
Organization and projects
Organization and projects
API keys
API keys
Policies
Policies
Spend limits
Spend limits
Usage and billing
Usage and billing
Authentication
The connection uses your current role in the organization you selected at sign-in. Review tool calls before approving changes.Permissions by role
Permissions by role
Creating an API key returns a secret. Store it securely and keep it out of shared conversations.
Reconnect or change organizations
Reconnect or change organizations
Your client refreshes authorization to keep you connected. If authorization expires, sign in again. To change organizations, reconnect and select the organization you want to use.
Rate limits
If a request is rate-limited, wait for the delay inRetry-After or the tool error’s retry_after_seconds before retrying.
Default request limits per minute
Default request limits per minute
Each management call counts against both your user budget and the shared organization budget.
Up to 5 management calls can run concurrently per user and 20 per organization. The MCP endpoint also limits requests to 300 per minute per IP address. Additional connection limits can restrict bursts.Organization budgets are shared with Administration API calls. Signing in again or using another client does not reset your user budget.Model-inference request and token limits are separate. See API rate limits.
Retry a request
Retry a request
- Honor the retry delay. If none is provided, use exponential backoff with jitter.
- Cap retry attempts and total retry time.
- For changes, reuse the original
idempotencyKeywhere supported. Do not automatically retry an operation whose result is uncertain.
Troubleshooting
Cannot connect
Cannot connect
Use
https://api.abliteration.ai/mcp and enable the server in your client. The client must support remote MCP over Streamable HTTP and OAuth.Sign-in required or 401
Sign-in required or 401
Reconnect through your client’s OAuth sign-in flow.
Permission denied or 403
Permission denied or 403
Check the connected organization and ask an owner or admin to confirm your role.
Resource not found
Resource not found
Check the resource ID. If you connected to a different organization, reconnect and select the organization that owns the resource.