Skip to content

chore(mcp): Add our MCP server to the official MCP registry #2510

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 16, 2025
Merged

chore(mcp): Add our MCP server to the official MCP registry #2510

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changeset/beige-flies-fail.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
"trigger.dev": patch
---

Add the mcpName property to the CLI package.json to allow publishing our MCP server to the Anthropic MCP registry
5 changes: 3 additions & 2 deletions packages/cli-v3/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"name": "trigger.dev",
"version": "4.0.2",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Version mismatch with server.json (4.0.2 here vs 4.0.3 in server.json).

If the MCP registry fetches the package immediately after this PR merges, pointing the manifest at 4.0.3 while the published package is 4.0.2 will break installs.

Two safe options:

  • Temporarily set server.json to 4.0.2 and update it to 4.0.3 in the release PR generated by Changesets, or
  • Bump this package.json to 4.0.3 in this PR and publish before submitting the registry entry.

Let me know which route you prefer and I’ll prep the diff.

🤖 Prompt for AI Agents 
In packages/cli-v3/package.json around line 3 the version is 4.0.2 but
server.json references 4.0.3, causing a registry manifest/install mismatch;
either (A) change server.json to 4.0.2 in this PR and plan to update it to 4.0.3
in the Changesets-generated release PR, or (B) bump packages/cli-v3/package.json
to 4.0.3 in this PR and publish the package before the registry entry lands;
pick one option and apply the corresponding fix (A: update server.json version
to 4.0.2; B: update package.json version to 4.0.3 and perform the publish step
so the published package matches server.json).

"description": "A Command-Line Interface for Trigger.dev (v3) projects",
"description": "A Command-Line Interface for Trigger.dev projects",
"type": "module",
"license": "MIT",
"repository": {
Expand All @@ -12,6 +12,7 @@
"publishConfig": {
"access": "public"
},
"mcpName": "io.github.triggerdotdev/trigger.dev",
"keywords": [
"typescript",
"trigger.dev",
Expand Down Expand Up @@ -154,4 +155,4 @@
}
}
}
}
}
31 changes: 31 additions & 0 deletions server.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
{
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-07-09/server.schema.json",
"name": "io.github.triggerdotdev/trigger.dev",
"description": "Official Trigger.dev MCP server to automate your Trigger.dev projects, write code, help debug runs, and get answers to questions about Trigger.dev",
"status": "active",
"repository": {
"url": "https://github.com/triggerdotdev/trigger.dev",
"source": "github",
"subfolder": "packages/cli-v3"
},
"version": "4.0.3",
"packages": [
{
"registry_type": "npm",
"registry_base_url": "https://registry.npmjs.org",
"identifier": "trigger.dev",
"version": "4.0.3",
"runtime_hint": "npx",
Comment on lines +11 to +18
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Align versions to what’s published to npm.

server.json references 4.0.3, while the CLI package.json is 4.0.2. If the registry ingests this now, npx resolution will fail.

Option A (safer now): set both fields to 4.0.2, then bump to 4.0.3 in the release PR.

-  "version": "4.0.3",
+  "version": "4.0.2",
@@
-      "identifier": "trigger.dev",
-      "version": "4.0.3",
+      "identifier": "trigger.dev",
+      "version": "4.0.2",

Option B: keep 4.0.3 but gate merge until 4.0.3 is actually published.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
"version": "4.0.3",
"packages": [
{
"registry_type": "npm",
"registry_base_url": "https://registry.npmjs.org",
"identifier": "trigger.dev",
"version": "4.0.3",
"runtime_hint": "npx",
"version": "4.0.2",
"packages": [
{
"registry_type": "npm",
"registry_base_url": "https://registry.npmjs.org",
"identifier": "trigger.dev",
"version": "4.0.2",
"runtime_hint": "npx",
🤖 Prompt for AI Agents 
In server.json around lines 11 to 18 the top-level "version" and the package
"version" are set to 4.0.3 while the CLI package.json is still 4.0.2, which will
break npx resolution; change both "version" and the package "version" in
server.json to 4.0.2 to match the published CLI (Option A), and plan a follow-up
release PR to bump both to 4.0.3 once that version is actually published.

"transport": {
"type": "stdio"
},
"package_arguments": [
{
"type": "positional",
"value": "mcp"
}
],
"environment_variables": []
}
]
}
Loading