feat: activate the Prismic MCP server when creating a repository#223
Merged
Conversation
angeloashmore
force-pushed
the
aa/mcp-activate-on-create
branch
from
b18cceb to
7a25ad6
Compare
New repositories are activated for the Prismic MCP server so agents can work with their content immediately, with no manual dashboard step. Best-effort: failures are ignored, since repositories will eventually have MCP enabled on the server by default. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
angeloashmore
force-pushed
the
aa/mcp-activate-on-create
branch
from
7a25ad6 to
950df48
Compare
lihbr
approved these changes
Jul 10, 2026
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves:
Description
New repositories now have the Prismic MCP server activated automatically when created via
prismic repo createorprismic init(includinginit --new). Agents can work with a new repository's content over MCP right away, with no manual activation step in the dashboard.The activation call is best-effort — any failure is ignored (
.catch(() => {})), so it can never break repository creation, and it's safe to remove once repositories are MCP-enabled server-side by default.Checklist
Additive and best-effort; existing behavior is unchanged (all existing tests pass).
Preview
How to QA
Then confirm MCP is active for the new repo — either in Settings → Prismic MCP in the dashboard, or by connecting the repo in an MCP-enabled agent. Creating a repo with a broken/unreachable activation endpoint should still succeed (the call is best-effort).
🤖 Generated with Claude Code
Note
Low Risk
Additive post-create side effect with errors ignored; core repo creation paths are unchanged on failure.
Overview
Repository creation now triggers a best-effort MCP activation so new repos are ready for agent/MCP use without a dashboard step. This applies to
prismic repo createand any flow that uses sharedcreateRepo(e.g.prismic init).A new
activateMCPclient POSTs tohttps://api.internal.{host}/mcp/activationwith the repo name andprismic-authcredentials. It runs after onboarding completion increateRepo; failures are swallowed with.catch(() => {})so creation never fails if MCP is down.Tests add
getMCPActivationStatusand assert status isactiveoractivatingafterrepo create.Reviewed by Cursor Bugbot for commit 4743f93. Bugbot is set up for automated code reviews on this repo. Configure here.