feat: add GitHub, Sentry, and New Relic MCP connectors - #694
Open
Valentyn (VaiYav) wants to merge 4 commits into
Open
feat: add GitHub, Sentry, and New Relic MCP connectors#694Valentyn (VaiYav) wants to merge 4 commits into
Valentyn (VaiYav) wants to merge 4 commits into
Conversation
Registers github, sentry, and newrelic as first-class MCP-backed connectors so users can ingest issues, PRs, alerts, and operational health signals into a personal OpenWiki without reusing the generic custom-mcp slot. - Extend ConnectorId union and CONNECTOR_IDS list - Wire each new id through createMcpConnector with read-only defaults - Add synthesis guidance for durable routing to themes/commitments - Surface the new connectors in onboarding source options and agent prompts - Update tool schemas (ingest, list_raw_items, read_raw_item, list/call_mcp_tool) Generated with Devin
🦋 Changeset detectedLatest commit: 01f0d3f The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Generated with Devin
Move project helper skills to the global registry while retaining the distributable OpenWiki integration bundle.
…ry-newrelic-mcp-connectors # Conflicts: # src/connectors/tools.ts
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
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.
Summary
Adds first-class MCP-backed connectors for GitHub, Sentry, and New Relic so users can ingest operational signals (issues, PRs, alerts, APM metrics) into a personal OpenWiki without reusing the generic
custom-mcpslot.Changes
src/connectors/types.ts: extendsConnectorIdunion withgithub,sentry,newrelic.src/connectors/registry.ts: registers each new id through the existingcreateMcpConnectorfactory, with read-only defaults and connector-specific descriptions.src/connectors/mcp-runtime.ts: adds the new ids toMCP_CONNECTOR_IDSandMcpConnectorId.src/connectors/tools.ts: updatesopenwiki_ingest_connector,openwiki_list_raw_items,openwiki_read_raw_item, and the MCP tool schemas to include the new connectors.src/ingestion/ingestion.ts: adds synthesis guidance for durable routing tothemes.md,commitments.md, and canonical source pages.src/setup/onboarding.ts: replaces the hardcodedisKnownConnectorIdwithisConnectorIdso any connector registered in the registry is accepted during onboarding normalization (this also fixeslangsmithbeing silently dropped).src/setup/credentials/constants.ts: adds GitHub, Sentry, and New Relic to source options and the personal onboarding template.src/agent/prompts/personal.ts: updates the agent prompt list of built-in connectors.test/: updatesingestion.test.ts,tools.test.ts, andonboarding.test.tsto match the expanded connector set.Motivation
Today users who want GitHub, Sentry, or New Relic data in their wiki have to squeeze everything through the
custom-mcpconnector, which means a single shared directory and a generic synthesis prompt. Dedicated connectors give each service:~/.openwiki/connectors/<id>/directory.openwiki ingest <id>target.git-repo, Sentry events with releases, and New Relic alerts with deployments.Test plan
pnpm run typecheckpasses.pnpm run buildpasses.test/connectors/tools.test.tstest/ingestion/ingestion.test.tstest/ingestion/langsmith-modes.test.tstest/setup/onboarding.test.tstest/setup/credentials/steps-derivations.test.tsopenwiki ingest githubis recognized, starts the configured MCP bridge, and routes data when enabled.Notes for reviewers
The MCP connector implementation is intentionally generic. Each new connector is a thin wrapper around
createMcpConnectorso users configure the actual transport (stdio or HTTP) in~/.openwiki/connectors/<id>/config.json. I opted not to add bespoke API code so that the PR stays focused on registry/tooling wiring and so users can plug in their preferred read-only MCP server for each service.Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>