Jam MCP
OFFICIAL SERVERHosted Jam server that feeds bug recordings, logs and network traffic to coding agents
Knock's hosted MCP server for building workflows and managing notification data in a Knock account
Official · knock.app Remote (hosted) · Streamable HTTP CommunicationDeveloper tools
Opens the app, which asks before it adds the server.
claude mcp add --transport http knock https://mcp.knock.app/mcphttps://mcp.knock.app/mcp{
"knock": {
"url": "https://mcp.knock.app/mcp",
"name": "Knock MCP Server"
}
}/mcp add --transport http knock https://mcp.knock.app/mcpKNOCK_SERVICE_TOKEN |
Optional: Optional Knock service token sent as 'Authorization: Bearer' for headless clients; skips OAuth and enables all capabilities. |
|---|
Knock is a notification platform: you define workflows that send email, SMS, push, chat and in-app messages to your users. This is Knock's own MCP server, run by Knock at mcp.knock.app/mcp, so there is nothing to install. An assistant connected to it can list and inspect workflows, templates, layouts, partials, guides and environments, build or edit workflows and their steps, trigger a workflow to test an integration, manage users, tenants and objects, read message delivery logs, and search Knock's documentation.
Access is split into capabilities chosen on the OAuth consent screen. Read resources, Manage resources and the Knock agent (the same conversational agent found in the Knock dashboard) are on by default; Debug (environments and message logs), Manage data (users, tenants, objects) and Documentation are off until you tick them. Signing in with a service token instead skips that screen and turns every capability on.
The server is built on the Knock Agent Toolkit, and its docs point to the toolkit's tools reference for the tool list. Its protected-resource metadata names mcp.knock.app itself as the authorization server and accepts bearer tokens in the Authorization header only (https://mcp.knock.app/.well-known/oauth-protected-resource).
A Knock account. Interactive clients sign in to it through OAuth in the browser. Headless use (CI, unattended agents) needs a Knock service token (knock_st_...) created under Settings > Service tokens in the dashboard. In Claude Code, run /mcp after adding the server to complete sign-in; in Cursor, sign in when prompted.
No tool deletes anything; Knock says this is on purpose. Workflows are not exposed as their own tools unless you opt in through Knock or your client. With every capability on the tool list can pass 50, which some clients warn about. It works only against the Knock API: local scaffolding, validation before push and offline work need the Knock CLI. Its docs note Cursor errors when the model is left on automatic selection; pick a model such as claude-sonnet-4.
Suits teams already on Knock who want an assistant to draft workflows, seed test users and tenants, trigger test sends or look into why a message did not arrive, without running anything locally. Because it is hosted and acts on your live account through the Management API, writes are real changes; keep the default capabilities narrow for exploration. For work on a checked-in repository of Knock resources, or offline, Knock points to its CLI instead. It is of no use without a Knock account.
listChannelslistCommitscommitAllChangespromoteAllCommitssearchDocumentationlistEmailLayoutsgetEmailLayoutcreateOrUpdateEmailLayoutlistEnvironmentslistGuidesgetGuidecreateOrUpdateGuidelistMessageTypescreateOrUpdateMessageTypegetMessagegetMessageContentgetMessageDeliveryLogsgetMessageEventslistObjectsgetObjectcreateOrUpdateObjectsubscribeUsersToObjectunsubscribeUsersFromObjectlistPartialsgetPartialcreateOrUpdatePartiallistTenantsgetTenantcreateOrUpdateTenantgetUsercreateOrUpdateUsergetUserPreferencessetUserPreferencesgetUserMessageslistWorkflowsgetWorkflowtriggerWorkflowcreateWorkflowcreateOneOffWorkflowSchedulecreateOrUpdateEmailStepInWorkflowcreateOrUpdateDelayStepInWorkflowcreateOrUpdateBatchStepInWorkflowcreateOrUpdateInAppFeedStepInWorkflowcreateOrUpdatePushStepInWorkflowcreateOrUpdateSmsStepInWorkflowcreateOrUpdateChatStepInWorkflow