Skip to content
AgoraGet started
Perystyl account

CRM MCP server: connect Agora to your assistant

Use your assistant to read CRM contacts, interactions and events, then prepare drafts with explicit permission. Agora’s MCP server runs over HTTP at https://agora.perystyl.com/mcp. The assistant never sends messages.

This guide records the Agora connection facts verified on . Connection documentation is available at Agora Connect.

Configure a client

Claude

Add a custom MCP connector, paste https://agora.perystyl.com/mcp, sign in, select your organisation and authorise the connection. Consultants have used this connection daily since October 2026.

Claude Code

Register the HTTP server:

claude mcp add --transport http agora https://agora.perystyl.com/mcp

Then authenticate the Agora connection in Claude Code. Authentication opens in your browser and returns through a localhost callback. Select the organisation and review the requested permissions before authorising. The URL contains no secret.

ChatGPT and Le Chat (Mistral)

An MCP OAuth connection is provided for by the protocol, but these clients have not yet been tested in real-world conditions with Agora. This guide does not promise a working connection for either client.

Connection and authentication

Endpoint
https://agora.perystyl.com/mcp: POST, HTTP transport.
Protected resource metadata
https://agora.perystyl.com/.well-known/oauth-protected-resource/mcp
Authorisation server
https://agora.perystyl.com

Authentication uses OAuth 2.1 with PKCE S256, public clients, Client ID Metadata Documents (CIMD) and dynamic client registration (DCR). A POST to /mcp without a token returns 401, with a WWW-Authenticate header pointing to the protected resource metadata.

Access tokens last 15 minutes. Refresh tokens last 30 days and rotate. Never put a token in the endpoint URL.

Permissions and safety

Consent is explicit. Choose an organisation at every authorisation. The default scope is read; offline_access is available for refresh access. Write scopes are unchecked by default, even when the client requests them.

Choose only the permissions needed for the task
ScopeAllows
readRead CRM data using the read tools listed below.
offline_accessRefresh access, with rotating refresh tokens.
write:contactsCreate, import and update contacts.
write:outreachPrepare outreach drafts and attachments, without sending.
write:mail_draftCreate and update the account holder’s Outlook drafts, without sending or deleting.

A write tool without the required consent is absent from tools/list. Calling it returns 403 insufficient_scope. Every call runs within the selected organisation; each tool call is logged with its client and consent, without token contents.

To revoke access, open Settings → Connections (Paramètres → Connexions) in Agora. Revocation takes effect immediately. Review every draft yourself and send it yourself.

The 19 tools

Read · 12 tools

  • search_contacts
  • search_topic_contacts
  • get_contact
  • get_company
  • list_interactions
  • get_interaction
  • list_deals
  • list_events
  • get_event
  • list_outreach
  • get_dashboard
  • get_stats

Write · 7 tools

write:contacts
create_contact, update_contact, import_contacts
write:outreach
prepare_outreach, attach_outreach_document
write:mail_draft
create_mail_draft, update_mail_draft

A reproducible demonstration

Use a demonstration organisation you are allowed to access. In Agora, prepare a fictional event called “Fictional Reuse Forum” with demonstration participants and a contact with an interaction dated within the last week. For the third request, authorise write:mail_draft for the account holder’s Outlook drafts. Without it, stop after reading the interactions.

After connecting Claude Code with the command above, enter the following requests. The result descriptions show the expected form, not a JSON schema or real customer data. Empty results are valid if your demonstration organisation has no matching records.

  1. Find the event context

    “Who should I follow up with before the event Fictional Reuse Forum? List the events, open the matching event and explain which records support your answer.”

    Tools: list_events, then get_event for the selected event.

    Result form: an event list, followed by the selected event’s details. The assistant summarises the available information and flags anything missing; a suggested follow-up is a recommendation to review.

  2. Read the dashboard

    “Show me my dashboard.”

    Tool: get_dashboard.

    Result form: dashboard information for the organisation selected during consent, followed by a plain-language summary.

  3. Prepare a follow-up draft

    “Draft a follow-up email to the contacts I met last week. First show the matching interactions; use only those records and leave missing information for me to complete.”

    Tools: list_interactions, then create_mail_draft with write:mail_draft consent.

    Result form: matching interactions, then an Outlook draft for the account holder to review. For example, a draft thanking a demonstration contact for the fictional reuse discussion. Nothing is sent.

Check that each result belongs to the selected organisation. Review the draft in Outlook without sending it. Revoke the connection in Agora when the demonstration is over.

Limits