Connector guide4-minute read13 MCP tools7 languages

Connect Front to Microsoft Copilot via MCP

Drive Front (collaborative inbox) from any AI agent: conversations, messages, contacts, tags, inboxes, teammates. 13 tools, API-key Bearer auth.

HCBy HelpCode teamUpdated 4 min read Open-source on GitHub

No credit card · 7-day trial · Self-host alternative available

Front

Front

Drive Front (collaborative inbox) from any AI agent: conversations, messages, contacts, tags, inboxes, teammates. 13 tools, API-key Bearer auth.

tools

13

Region

INTL

Category

Customer Support

Authentication

Bearer Token

Required env vars

FRONT_API_TOKEN
Install in one click on Cloud

7-day free trial · No credit card

  • 7-day free trial
    No credit card required
  • GDPR & SOC 2 ready
    EU data residency, audit logs
  • Open-source on GitHub
    Open source · AGPL-3.0
  • Works with ChatGPT, Claude, Gemini
    Any MCP-compatible client

Summary

Drive Front (collaborative inbox) from any AI agent: conversations, messages, contacts, tags, inboxes, teammates. 13 tools, API-key Bearer auth.

Guided setup

Connect Front to Microsoft Copilot in 2 minutes

Start a free trial on AnythingMCP Cloud, connect Front in the guided setup, then add your MCP URL to Microsoft Copilot. No code and no server to run.

No credit card · 7-day trial · Self-host alternative available

Try asking

Example prompts for Front

Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.

Front · live via MCP
Share
Opus 4.7

Claude is AI and can make mistakes. Please double-check responses.

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

Front + Microsoft Copilot

Drive Front (collaborative inbox) from any AI agent: conversations, messages, contacts, tags, inboxes, teammates. 13 tools, API-key Bearer auth.

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:

FRONT_API_TOKEN

Step 1 — Get credentials

Setup:

  1. Sign in to Front → Settings (top-right) → Developers → API Tokens → Create API Token.
  2. Pick scope: private (full-access to all inboxes/conversations) or scoped to a specific inbox/role.
  3. Copy the token. Set FRONT_API_TOKEN.

Authentication: Authorization: Bearer ${FRONT_API_TOKEN}.

Front's tile model:

  • Conversation = a thread between your team and one or more contacts. Has status (open/archived/spam/deleted), assignee, inbox, tags.
  • Message = each inbound/outbound email, SMS, chat, etc. within a conversation.
  • Contact = an external entity (a customer). …

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 Front 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

ToolWhat it does
front_meReturn the API token's identity (id, name, email)
front_list_inboxesList inboxes the token can access
front_list_conversationsList conversations with optional filtering
front_get_conversationFetch a single conversation including assignee, tags, recipient handles, links to messages/comments
front_list_conversation_messagesList all messages in a conversation chronologically
front_send_replySend a reply (new message) in an existing conversation
front_add_commentAdd an internal comment (private note) to a conversation
front_update_conversationUpdate conversation status, assignee, or tags
front_list_contactsList contacts (external entities)
front_get_contactFetch a contact with all handles[] (email/phone/twitter/custom)
front_create_contactCreate a contact
front_list_tagsList tags
front_list_teammatesList teammates (Front users)

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

Was this guide helpful?

Connect Front to Microsoft Copilot in 2 minutes

Start a free trial on AnythingMCP Cloud, connect Front in the guided setup, then add your MCP URL to Microsoft Copilot. No code and no server to run.

Related guides