MCP

Connect MCP-capable AI clients to Cossistant so agents can read the support context your signed-in teammate can already access.

Endpoint:

Copyhttps://api.cossistant.com/mcp

The hosted MCP server uses remote HTTP MCP with OAuth. Your client will open a browser login flow when authentication is needed. Do not paste a Cossistant API key, bearer token, or client secret into your MCP config.

Access is scoped to your Cossistant account. Agents can only read websites and support data available to the teammate who signs in. OAuth requests the support:read scope.

Install

Cursor

Create or update .cursor/mcp.json in your project, or ~/.cursor/mcp.json for a global setup:

Copy{
  "mcpServers": {
    "cossistant": {
      "url": "https://api.cossistant.com/mcp"
    }
  }
}

Restart Cursor or reload MCP after saving the file. When Cursor asks for authentication, complete the browser login flow.

Claude Code

Copyclaude mcp add --transport http cossistant https://api.cossistant.com/mcp

Then open Claude Code and run:

Copy/mcp

Use the MCP status view to authenticate with Cossistant in your browser.

OpenCode

Add Cossistant to opencode.json:

Copy{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cossistant": {
      "type": "remote",
      "url": "https://api.cossistant.com/mcp",
      "enabled": true
    }
  }
}

Restart OpenCode or reload MCP so it discovers the new server.

Manual

For clients that accept an mcpServers object, use:

Copy{
  "mcpServers": {
    "cossistant": {
      "type": "http",
      "url": "https://api.cossistant.com/mcp"
    }
  }
}

Some clients call remote HTTP transport streamable-http. Keep the same URL if your client uses that name.

What agents can do

The first Cossistant MCP tools are read-only:

Mutation tools like replying, resolving, or changing priority are not exposed yet.

Tool inputs and outputs

Select a website with exactly one of websiteId or the exact websiteName for every tool except cossistant_list_websites.

Tool errors are returned as MCP errors without database internals. A missing or ambiguous website selector, inaccessible resource, invalid cursor, or expired OAuth session should be corrected rather than retried blindly.

The hosted endpoint currently allows 60 MCP HTTP requests per minute per IP/auth subject. Respect rate-limit headers and retry after the server's window; do not run parallel unbounded pagination.

Try it

Ask your agent:

CopyList my Cossistant websites.

CopySearch Acme Support knowledge for billing cancellation.

CopyShow recent open conversations for Acme Support.

CopyOpen conversation <conversationId> and summarize the latest customer issue.

Troubleshooting

• Reconnect or reload MCP after editing config.
• Use your client's MCP status view to complete OAuth.
• Confirm you are signed in with a Cossistant account that has access to the website.
• Remove any Authorization headers if OAuth does not start.
• In OpenCode, use opencode mcp list, opencode mcp debug, and opencode mcp logout cossistant to inspect or clear auth.
• In Claude Code, open /mcp to inspect the server and clear/re-authenticate it.
• In Cursor, use its MCP status/login controls after reloading the config.
• Revoke access by logging the Cossistant server out in the client or revoking the corresponding OAuth session in your account security settings.