How to Connect Freshsales to Microsoft Copilot via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Freshsales, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

Freshsales + Microsoft Copilot

Freshsales (Freshworks CRM) from any AI agent: search and filter contacts, accounts and deals, move deals through pipeline stages, add notes, plan tasks and appointments, log sales activities and manage marketing lists. Works with a per-user API key and the bundle URL of your account.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

FRESHSALES_BUNDLE_URL, FRESHSALES_API_KEY

Step 1 — Get credentials

Setting up takes about 2 minutes. You need a Freshsales (Freshworks CRM) account.

1. In Freshsales click your profile picture, then Profile Settings, and open the API Settings tab.
2. Copy Your API key into FRESHSALES_API_KEY. The connector sends it as Authorization: Token token=<key>, so paste only the key.
3. On the same tab copy the bundle alias (the address of your account) into FRESHSALES_BUNDLE_URL, for example https://acme.myfreshworks.com/crm/sales. Accounts created before the Freshworks suite use https://acme.freshsales.io. Leave out /api and any trailing slash.
4. Install the connector and run freshsales_list_owners: it lists the users of the portal and confirms key and address.

Every call acts with the permissions of the user whose key is set: records outside that user's scope stay invisible. Use the key of a user who sees the data the team needs.

Start here: freshsales_list_owners gives the user ids used as owner_id. freshsales_list_selector reads a picklist (territories, pipelines and stages, currencies, deal types and reasons, lead sources, industry and business types, campaigns, contact statuses, lifecycle stages, sales activity types and outcomes) and returns the ids to use when writing. freshsales_list_pipeline_stages gives the stages of one pipeline. freshsales_list_fields lists the fields of contacts, accounts, deals or sales activities, including custom fields: their internal names start with cf_ and go in custom_field.

Finding records:

• freshsales_search: text search by name or email across contacts, accounts, deals and users. include takes the singular names contact, sales_account, deal and user; a plural returns nothing.
• freshsales_lookup: exact match on one field, for example contacts by email, or contacts, accounts and deals by name or a custom field value.
• freshsales_filtered_search: rules on fields (exact matches, ranges, lists), returning full records.
• Lists always go through a saved view: freshsales_list_views gives the view ids (for example "All Contacts" or "My Deals"), then freshsales_list_contacts, freshsales_list_accounts or freshsales_list_deals read the view with sorting.

Contacts, accounts and deals: freshsales_get_contact, freshsales_get_account and freshsales_get_deal read one record and embed related records with include (for example sales_accounts,deals,notes). freshsales_list_contact_activities shows the timeline of a contact (emails, calls, notes, field changes, web visits). To write, the AI uses freshsales_create_contact (at least an email or a last name), freshsales_update_contact, freshsales_upsert_contact (create or update by email or another unique field), freshsales_create_account (unique name), freshsales_update_account, freshsales_create_deal (name and amount are required) and freshsales_update_deal. A deal moves when deal_stage_id is set to a stage of its pipeline; won and lost are stages too, and a lost deal can carry a deal_reason_id. Updates change only the fields passed.

Notes, tasks, appointments and activities are attached to a record with targetable_type (Contact, SalesAccount or Deal) and targetable_id:

• Notes: freshsales_create_note, freshsales_update_note.
• Tasks: freshsales_list_tasks (one filter per call: open, due_today, due_tomorrow, overdue or completed), freshsales_get_task, freshsales_create_task, freshsales_update_task, freshsales_complete_task.
• Appointments: freshsales_list_appointments (open for upcoming, past for past ones; older portals use upcoming), freshsales_get_appointment, freshsales_create_appointment, freshsales_update_appointment. Attendees are users (FdMultitenant::User) or contacts (Contact).
• Sales activities such as logged calls and visits: freshsales_list_sales_activities, freshsales_get_sales_activity, freshsales_create_sales_activity.

Marketing lists: freshsales_list_marketing_lists, freshsales_list_marketing_list_contacts, freshsales_add_contacts_to_list and freshsales_remove_contacts_from_list (the contacts themselves are kept).

Leads: current Freshsales accounts keep prospects as contacts with a lifecycle stage; there is no separate leads module. The AI filters contacts by lifecycle stage through a view or freshsales_filtered_search.

Switched off at install: nothing. The connector has no delete tools, so it cannot remove contacts, accounts, deals, notes, tasks or appointments. Creating and updating records changes your live CRM, so ask the AI to show the fields before it saves.

Data formats: timestamps come back in UTC or with an offset (2026-02-13T23:27:49Z). Date inputs accept YYYY-MM-DD or ISO 8601; without a zone UTC is assumed. Amounts are in the currency of the deal; base_currency_amount is converted to the portal currency. Blank fields are null. Records embedded with include arrive in separate top-level arrays (users, sales_accounts, deals) next to the record, linked by id.

Paging: lists take page (from 1) and per_page (default 25, at most 100) and return meta.total_pages and meta.total. freshsales_search returns 10 results by default, at most 100.

Limits and common errors: 1000 requests per hour per account; above that Freshsales answers 429. 401 means a wrong or missing key, 403 that the user lacks the permission or the feature is not on the plan, 404 a wrong id or a wrong bundle URL. Validation errors return 400 with errors.message.

The connector does not delete records, does not send emails and does not change portal settings, fields or pipelines.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Microsoft Copilot

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.

1. In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
2. Enter a Server name (for example AnythingMCP), a Server description that says what the connector does, and the Server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server.
3. Under authentication, choose API key, set Type to Header and the header name to X-API-Key, then select Create.
4. In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
5. Try it in the agent's Test pane: ask for something that needs the Freshsales tools.
6. Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.

Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.

Available tools

Example prompts

• "Find the contact [email protected] and show me her open deals and the latest notes on her record."
• "List my open deals that are expected to close this month, with amount and stage."
• "Move the Acme renewal deal to the Negotiation stage and add a note that the quote was sent."
• "Which of my tasks are overdue? Group them by the linked account."
• "Log a 30-minute call with Tom Becker for today and create a follow-up task for next Tuesday at 10:00."

FAQ

Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.

What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.

The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT
• Connect to Cursor
• Connect to Gemini
• Connect to Meta Muse