Skip to content

docs: add report-only Sem MCP cookbook example - #679

Open
rs545837 wants to merge 1 commit into
cobusgreyling:mainfrom
rs545837:docs/sem-mcp-cookbook
Open

rs545837 wants to merge 1 commit into
cobusgreyling:mainfrom
rs545837:docs/sem-mcp-cookbook

Conversation

@rs545837

Copy link
Copy Markdown

Summary

I'm the maintainer of Sem. This adds an optional MCP cookbook entry for report-only local code navigation: locate an entity, request related source, record incomplete evidence, and hand off before changing code.

Three example files only; no default tools, runtime behavior, skills, registry or permissions changed. The pinned stdio configuration requires an explicit trusted checkout. The guide warns that the full server is not read-only, that repository selection is not a sandbox, and that structural evidence does not replace builds/tests.

Verification

An independent agent followed the repository's loop-verifier skill and approved the scoped contribution for maintainer review:

  • JSON configuration, nine local links/anchors, and git diff --check passed.
  • Live MCP SDK test loaded the actual example configuration, replacing only the repository placeholder with a temporary Git fixture.
  • Eight tools discovered; sem_find returned parse_config at config.py:1.
  • The context query returned the target source plus its load_config caller with no tool error.
  • No model calls, repository validation commands, or edits through MCP were performed.

Content-only contribution (CONTRIBUTING path A); application/tool package suites were not run. This verifies the connector, not session-speed claims.

Checklist

  • Linked from the MCP cookbook index
  • No secrets or internal URLs
  • Safety-sensitive content links to human gates and untrusted-input guidance
  • No live state files added

AI assistance was used for implementation and verification. Maintainer review is requested; no auto-merge.

@github-actions

Copy link
Copy Markdown
Contributor

Thanks @rs545837 for contributing a tool example — visible, reviewable PRs like this grow the reference for everyone.

What happens next

  • Maintainer aims for same-day review on story, adopter, and scoped docs/example PRs (CONTRIBUTING.md).
  • good first issue PRs: comment on the linked issue so we can assign and close on merge.

More ways to help

— loop-engineering maintainers

@cobusgreyling

Copy link
Copy Markdown
Owner

Leaving this open. The merge state is UNSTABLE, and there is no approving review.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants