Metaventus MCP server
Metaventus exposes an MCP server (Model Context Protocol), the open standard that connects AI assistants to software. Claude, ChatGPT, Microsoft Copilot, Cursor and any compatible MCP client can read and update your CRM and meetings, in plain language:
"Create the contact Jeanne Martin at Acme and link her to the company." "Which meetings do I have next week? Offer Paul a slot on Thursday."
https://mcp.metaventus.com/mcp
Connecting
- In your AI, add a custom connector (Claude: Settings → Connectors; ChatGPT: Settings → Connectors in developer mode; Copilot Studio: Tools → MCP) with the address above.
- The AI sends you to Metaventus. Sign in, review the requested permissions, then click Authorize.
- Done. The connection appears in My profile → AI applications, where you can cut it at any time.
No key to copy: the connection uses OAuth 2.1 (mandatory PKCE, dynamic client
registration, tokens bound to the https://mcp.metaventus.com/mcp resource).
What the AI can do
The AI acts with your Metaventus permissions, never more: a tool only appears if your role grants the matching permission, and every call is checked again in real time.
| Scope | Tools |
|---|---|
crm:read | search_crm, list_crm_records, get_crm_record, get_crm_record_activity, list_crm_notes, find_crm_duplicates |
crm:write | create_crm_record, update_crm_record, link_contact_to_company, add_crm_note |
booking:read | list_event_types, find_available_slots, list_events, get_event |
booking:write | create_event, reschedule_event, update_event, add_event_invitee, remove_event_invitee, cancel_event |
Tools that change, cancel or notify someone are flagged to the client (readOnlyHint,
destructiveHint, openWorldHint) so it asks for your confirmation. Not available in
this version: permanent deletions, bulk operations, sending messages.
For administrators
In Admin center → AI applications:
- turn AI applications on or off for the whole organization (turning them off cuts every connection immediately);
- cap the scopes (read-only, for example);
- see and revoke every connection of every member;
- review the activity log of every action (who, which application, which tool, which record, result), kept for one year. Arguments are not stored in clear text.
A Metaventus support session can never authorize an application on a customer's behalf.
With an API key (automations, developers)
A secret API key can also authenticate on the MCP server, on two conditions: the MCP access option is turned on for the key (Admin center → API keys), and the organization policy allows keys. The key keeps its permissions and IP restrictions, and never gets more than its creator's permissions.
curl https://mcp.metaventus.com/mcp \
-H "Authorization: Bearer sk_live_…" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Technical details
| Transport | Streamable HTTP (POST /mcp, JSON responses), versions 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05 |
| Discovery | /.well-known/oauth-protected-resource (RFC 9728), /.well-known/oauth-authorization-server (RFC 8414) |
| Authorization | /oauth/authorize (code + PKCE S256), /oauth/token, /oauth/register (RFC 7591), /oauth/revoke (RFC 7009) |
| Tokens | access 1 h; refresh 30 days, rotated on every use — a replay revokes the connection |
| Limits | 60 tool calls per minute per connection, 300 per organization |
| Hosting | European Union (Frankfurt) |