Open MCP server
Give your AI agents a better starting point.
Bring our engineering playbooks, release-evidence rubric, and planning tools into your own MCP-compatible assistant. Public, read-only, and ready to inspect.
Connect using Streamable HTTP
One endpoint.
Useful engineering context.
In a client that supports remote MCP, add this URL as a Streamable HTTP server. Client setup and subscription requirements vary.
https://dotnetguides.com/mcp
No API key is needed for these public tools. The server makes no LLM calls. Your AI client and hosting resources may have their own costs.
Inspect the server implementationTry this with your connected assistant
Use Mottobits to plan an AI-assisted regression-coverage sprint for our legacy app. We have partial automated tests. List the relevant playbooks. Show prerequisites, deliverables, and acceptance evidence for the first slice. Distinguish assumptions from facts. Do not request code or production data.
- Public knowledge and categorical planning inputs only
- No source-code upload, credentials, or repository access
- No side effects, write actions, or paid model calls
- A planning aid; your engineer owns the release decision
Available tools
A small, inspectable toolkit.
| Tool | What you get |
|---|---|
list_playbooks | Public playbook titles and links. |
get_playbook | A complete, source-backed engineering playbook. |
assess_release_readiness | A self-reported evidence score, unknowns, critical gaps, and next steps. |
get_release_safety_checklist | A practical checklist for an agreed release boundary. |
plan_first_sprint | A bounded first-sprint plan based on your goal and test maturity. |
get_engagement_options | Transparent package pricing, scope, and the next contact step. |
No tool inspects a repository, certifies release safety, or executes a change. Inputs sent through MCP reach our hosted endpoint; the browser assessment runs locally.