Integrations — MCP Connector

MCP (Model Context Protocol) is an open standard that lets AI assistants use tools from other applications. The edMission MCP server connects the CRM to assistants like Claude and ChatGPT, so you can search leads, check your work queue, log notes, schedule follow-ups and more, just by asking in plain English.

It acts as you. Every request runs through the same CRM permissions you have in the browser, so you only see and change what your role already allows.

• Claude Code installed and signed in (a recent version — run claude update if unsure).
• An active edMission CRM account with CRM access.
• Your organization must have MCP access enabled — it's off by default for new organizations. If sign-in says access isn't allowed, ask your edMission admin to turn it on.

Step 1 — Install. Open a terminal and run:

claude mcp add --transport http --scope user \
  edmission https://api.edmissioncrm.com/mcp

Confirm it was added with claude mcp list — right after install, edmission will show as needing authentication. That's expected.

Step 2 — Sign in (one-time per session). Start Claude Code (claude), type /mcp, select edmission, and choose Authenticate. Your browser opens the edMission sign-in page — sign in with email OTP, an SMS OTP to your registered phone, or Google (where enabled).
Step 3: Pick the organization this connection should use, review the consent screen, and click Allow.
Step 4: The browser returns you to Claude Code, and edmission shows as connected. Test it by asking: "Who am I in edMission?"

The session lasts about 24 hours and extends while you keep using it. When it expires, run /mcp → Authenticate again.

• What should I do next today?
• Find the lead Priya Sharma and summarise her recent activity and notes.
• Which of my follow-ups are overdue?
• Add a note to this lead: called, interested in the Sept intake, will send documents Friday.
• Schedule a follow-up with this lead tomorrow at 11am.
• Move this lead to the Application Submitted stage. (you'll be asked to confirm)
• Why is this lead's score so high?

• Same permissions as the CRM. The MCP server adds no access of its own — if you can't do it in the browser, you can't do it here.
• Confirmation for high-impact changes. Stage changes and reassignments must be confirmed before they apply.
• No deletions. No tool deletes leads.
• Audited. Changes are recorded with you as the actor, marked as made via MCP.
• Rate limited. A per-user limit on tool calls per minute protects the CRM.