Modem MCP Server gives AI agents a unified view of customer feedback from Slack, Discord, GitHub, Zendesk, Intercom, email, and call transcripts, letting them search customer issues, feature requests, and complaints, analyze affected users and companies, update topics, and trigger actions through Modem’s agent.
DeepSeek Harness (DSH) is DeepSeek's agent harness. Each MCP server is one plugin entry in your project config.
This guide connects Modem MCP to DeepSeek Harness through MewCP, so DeepSeek Harness can use Modem MCP's 16 tools, like modem_agent_invoke, modem_agent_get_run and modem_agent_send_message, without your Modem MCP credentials ever reaching the app.
Modem MCP signs in through managed OAuth. MewCP stores the token encrypted, refreshes it before it expires and injects it only at call time. Your agent never holds it, so it can never leak it.
More apps
Ask your AI to find companies, verify email addresses, and build leads lists with Hunter’s MCP.
Search Apollo's B2B contact and company database, enrich records in bulk, and manage email sequences from your connected Apollo account.
Brevo's marketing and CRM platform — manage contacts, lists and segments, send transactional and campaign email, run SMS and WhatsApp campaigns, and track deals and companies
HubSpot connects AI agents to CRM data and business workflows, enabling them to search and manage contacts, companies, deals, tickets, and engagement records, and access HubSpot tools through its remote MCP server.
Other clients
Modem MCP works the same way in every client below. Pick yours for its own guide.
Free to start.
Scope access to the exact Modem MCP tools and accounts you allow, work and personal side by side. Anything outside that scope is refused at call time, even when the model asks for it.
Each call is logged: what ran, on which account, and whether it worked. Failures come back structured, so the agent knows whether to retry instead of guessing.
Every app sits behind one secure MCP URL, and there is no server for you to deploy or keep running. Add an integration in the dashboard and it is live on the next call, with no config to change and no new credentials to wire up. Tools load only when a task needs them, so your agent stays fast and focused however many apps you connect.
In your DSH project, or the patch file you mount plugins from.
One plugin instance is one MCP server. Add this to your plugin list.
Tools register as mcp__mewcp__<tool_name>. Sign in when the browser window opens.
Start a new chat and ask: "List the tools you can use from MewCP." You should see your connected apps.
Start a durable Modem agent conversation. Returns immediately with conversation_id and run_id; poll modem_agent_get_run for the result. Before your first call, read the skill: `modem_skills({ name: "agent-runs" })`.
Get the current status and terminal result of a durable Modem agent run.
Start a durable follow-up turn in an existing MCP conversation.
Cooperatively cancel one exact durable Modem agent run. Completed external actions are not reversed.
Skills that teach you how to use THIS Modem MCP server's tools. Call before your first `search_modem`, `modem_agent_invoke`, or write-tool call, or when unsure which Modem tool to use. Pass `name` for the full skill, one of `search-modem`, `agent-runs`, `write-tools`. Omit `name` to list them with descriptions. This is not the Skills page in dashboard settings.
Answer a natural-language question about your Modem data and get matching rows back. Read-only. It does not run the full Modem agent or spend agent credits. Send a `question`, or send only the `cursor` from a previous result to fetch its next page. Topic `priority` in the rows is an integer: very_low (-100), low (-50), default (0), high (50), very_high (100). Before your first call, read the skill: `modem_skills({ name: "search-modem" })`.
Search or read Modem's public docs to answer how Modem works: setup, integrations, this MCP server and its scopes, the API, and automations. Not for your organization's data; use `search_modem` for that. Send a `query` to search, or a `page` path from a search result (such as `api/modem-mcp-server`) to read the whole page. Send exactly one. Read-only, spends no agent credits.
Update a single topic (priority, lifecycle state, archived status, issue type, or keywords). Before your first call, read the skill: `modem_skills({ name: "write-tools" })`.
Update multiple topics at once (e.g. archive or re-prioritize a set of topics). Before your first call, read the skill: `modem_skills({ name: "write-tools" })`.
Merge one or more source topics into a target topic. Before your first call, read the skill: `modem_skills({ name: "write-tools" })`.
Create one or more companies in the organization. Before your first call, read the skill: `modem_skills({ name: "write-tools" })`.
Update fields on one or more existing companies. Before your first call, read the skill: `modem_skills({ name: "write-tools" })`.
Merge one or more source companies into a target company. Before your first call, read the skill: `modem_skills({ name: "write-tools" })`.
Associate one or more people with a company. Before your first call, read the skill: `modem_skills({ name: "write-tools" })`.
Update fields on one or more existing people. Before your first call, read the skill: `modem_skills({ name: "write-tools" })`.
Merge one or more source people into a target person. Before your first call, read the skill: `modem_skills({ name: "write-tools" })`.
