Skip to main content
The Convosphere MCP server exposes Convosphere product APIs as callable tools for AI clients such as Cursor. Tools run with the authenticated user’s OAuth context and, when available, are tracked against the user’s default MCP API key.

Tool access model

MCP tools use two layers of authorization:
  1. MCP authentication verifies the Cursor OAuth access token.
  2. Application authorization checks user role, plan, ownership, and route-level permissions.
This means a tool can be connected correctly but still return 403 when the current user is not allowed to perform the action. For example, canCreateAgent can return limitReached on a free plan after the user already has one agent.

Core tools

These tools are always available and are the best first tests after connecting. Example:

Health and diagnostics

User and account tools

Mutation tools such as updateUserProfile, updateUserPreferences, updateUserTheme, changePassword, and deleteUserAccount should only be tested with a test account.

Agents and analytics

Example:

Conversations and messages

Conversation detail tools require both id and threadId.

Knowledge, training, and Notion

Tools that upload files, add URLs, add Q&A, sync Notion, reindex data, or start fine-tuning can change data or start background jobs. Test them with disposable data.

Tickets and notifications

Create, update, delete, mark-read, and bulk notification tools mutate data.

Integrations and providers

Creating, updating, deleting, OAuth callbacks, and webhook handlers can create or modify integration records.

Public and pricing tools

Admin-only tools

Some tools are exposed through MCP but still require admin permissions in the application layer. A normal user should expect 401 or 403 for these tools. Examples include:
  • getSchedule
  • listLeads
  • Admin analytics, user, ticket, pricing, configuration, and super-admin tools
Do not bypass these guards for normal MCP users.

Safe test checklist

Use this checklist after a new MCP connection:
1

Verify identity

2

Verify server health

3

Verify usage tracking

4

Verify user-scoped proxying

5

Verify agent reads

Unsafe test categories

Do not run these on a real account unless the intent is explicit:
  • Account deletion and password changes
  • Create, update, and delete tools
  • Payment and Razorpay webhook tools
  • Webhook receiver tools
  • File upload and URL ingestion tools
  • Fine-tuning start tools
  • Notion sync tools
  • Ticket creation tools that notify users or admins
Use a test user, test agent, and disposable records for full end-to-end mutation testing.