mcp

MCP-native AI SRE: ask what's broken in production, get a reviewed GitHub fix PR.

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

    What data it sees

    Do you need an account

    No: the server works without sign-in

    MCP-native AI SRE: ask what's broken in production, get a reviewed GitHub fix PR.

    How to connect

    How to connect mcp to Claude

    The server address to paste into Claude settings:

    https://aient.ai/mcp

    1. Open Claude (claude.ai or the desktop app).
    2. Go to Settings → Connectors.
    3. Click Add custom connector.
    4. Paste the server address copied below into Remote MCP server URL and click Add.
    5. In a chat, click + → Connectors and switch the new connector on.

    Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

    Authorization

    After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

    How to connect mcp to ChatGPT

    The server address to paste into ChatGPT settings:

    https://aient.ai/mcp

    1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
    2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
    3. Open Settings → Connectors and click Create.
    4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
    5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
    6. In a new chat open + → Apps/Connectors and enable the connector.

    OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

    Authorization

    On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

    How to connect mcp to Cursor

    The server address to paste into Cursor settings:

    https://aient.ai/mcp

    Fastest: click Open in Cursor below and confirm the prompt.

    Manually:

    1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
    2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
    3. Save the file. The server appears in the MCP list; authorize it there if asked.

    Authorization

    If the service needs sign-in, an authorize button appears next to the server in the MCP list.

    Server tool list (2)

    Raw names from tools/list. Only developers need these.

    signupCreate an Aient account from an email address, or get a sign-in code for an existing one, with no browser and no token. **When to use**: you have no Aient access token and the user wants a workspace, or an earlier `verify_email` answered `workspace_unavailable` or its token expired. Ask the user which email address to use. **What happens**: Aient emails a 6-10 digit one-time code to that address. Read the code from that inbox (or ask the user for it), then call `verify_email` with the same email and the code. An address that already has an Aient account receives a sign-in code from this tool instead of a new account; verify_email then returns a token for that account's workspace, preparing the workspace first if an earlier signup never finished. The emailed code is a Supabase Auth credential: it grants this MCP token, and the same email carries a browser sign-in link, so treat both as secrets. **Limits**: a few attempts per minute per address.
    verify_emailConfirm the code Aient emailed after `signup` and receive the access token for this MCP server. **Returns**: `access_token` (a Bearer token for this server, valid for `expires_in` seconds), `organisation_id`, and `user_id`. For an address that already had an account, the token belongs to that account's existing workspace; a workspace that was never prepared is prepared now. Reconnect to this MCP server sending "Authorization: Bearer <access_token>" on every request. Then call `verify_connection` and `get_activation_status` and follow its `nextActions` to finish onboarding. The token is not refreshable: when it expires, call `signup` and `verify_email` again. **Errors**: `confirmation_expired` means the code is too old (call `signup` again); `confirmation_failed` means it did not match; `workspace_unavailable` means the code was accepted but the workspace could not be prepared (call `signup` again for a new code, never `verify_email` with the used one).