modem.dev
Modem is a product-feedback and workflow platform for developer-facing teams. It aggregates conversations from tools like Slack, Discord, GitHub, Zendesk, Intercom, and email into prioritized topics and lets teams query or act on that context with AI.
modem.dev exposes four developer integration surfaces: a REST API at `api.modem.dev/v1`, a separate ingest HTTP API at `ingest.modem.dev`, a hosted MCP server at `mcp.modem.dev/mcp`, and the `modem` CLI published as `@modem-dev/cli`; all require authentication via either Modem API keys or Modem OAuth for MCP.
- Modem MCP serverdetected
- Modem Ingest APIdeclared
- Modem APIdeclared
- Modem CLIdeclared
Point your MCP client at the server URL and approve access in the browser. The server supports OAuth Dynamic Client Registration (RFC 7591), so the client registers itself automatically — no developer-portal app, client_id, or client_secret to create.
$ modem auth loginAcquired by the CLI — running modem auth login opens the auth flow and stores the credential.
In the Modem dashboard, open Organization → Projects, choose the target project, and under Public Keys create or copy a key. Only org admins and owners can manage these keys. Despite the name, docs say to treat it as a server-side secret and send it in the x-modem-public-key header to POST https://ingest.modem.dev/ingest.
conventions · 5/8 published
- integrations.json✓https://modem.dev/.well-known/integrations.json
- llms.txt✓https://modem.dev/llms.txt
- API catalog✓https://modem.dev/.well-known/api-catalog
- OpenAPI document✓https://modem.dev/openapi.json
- MCP server card✓https://mcp.modem.dev/mcp
- OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing