Match the project to your task before installing it.
MCP Tool Integration · Public
mcp-ts-template
MCP tool integration project for safely connecting external tools, services, or data sources to an AI host.
Check whether this project matches your task before installing it.
What it can doMCP setup guidance, host configuration checks, tool permission boundaries, recovery steps, and acceptance checksReview the portable capability path.
Before continuingVerify in a sandboxDo not treat a preview pack as a proven local install.
GitHub snapshotstars unavailableforks unavailable · contributors unavailable
Publication status · 2026-05-25
What is mcp-ts-template?
- mcp-ts-template helps connect external tools, services, or data sources to AI hosts that support MCP.
- Best fit: Developers who need Claude, Cursor, Codex, or another MCP-capable AI host to call external tools safely.
- Not for: Not for users who cannot change host configuration, grant tool permissions, or isolate network, file, and credential access.
- Capability added to an AI workflow: MCP setup guidance, host configuration checks, tool permission boundaries, recovery steps, and acceptance checks
- First safe verification step: Verify the MCP server command, permission scope, and rollback path in a non-primary host configuration first.
- Verification state: source, Quick Start, and sandbox install checks are recorded as passed.
- Top risk: The main risk is unclear tool, filesystem, network, or credential boundaries contaminating host configuration or exposing sensitive data.
- Evidence base: https://github.com/cyanheads/mcp-ts-template, https://registry.modelcontextprotocol.io/v0.1/servers/io.github.cyanheads%2Fmcp-ts-template/versions/3.0.9, Human Manual, Pitfall Log
01
Quick decision
Use this section to decide whether the project is worth a deeper read.MCP tool integration project for safely connecting external tools, services, or data sources to an AI host.
stars unavailable · forks unavailable
02
What it can do
Translate the upstream project into concrete capabilities the user can judge before installing.Repository Overview
Related topics: Entrypoints and Runtime Surface, Architecture Evidence Map, Operations and Verification Boundaries
Source: https://github.com/cyanheads/mcp-ts-template / Human Manual
Entrypoints and Runtime Surface
Related topics: Repository Overview, Architecture Evidence Map, Operations and Verification Boundaries
Source: https://github.com/cyanheads/mcp-ts-template / Human Manual
Architecture Evidence Map
Related topics: Repository Overview, Entrypoints and Runtime Surface, Operations and Verification Boundaries
Source: https://github.com/cyanheads/mcp-ts-template / Human Manual
Operations and Verification Boundaries
Related topics: Repository Overview, Entrypoints and Runtime Surface, Architecture Evidence Map
Source: https://github.com/cyanheads/mcp-ts-template / Human Manual
Doramagic Pitfall Log
Source-linked risks stay visible on the manual page so the preview does not read like a recommendation.
Source: Doramagic discovery, validation, and Project Pack records
Sources: https://github.com/cyanheads/mcp-ts-template, Human Manual, Project Pack evidence, and downstream validation signals.
03
Community Discussion Evidence
Project-level external discussion stays visible on the detail page, not only inside the manual.Community Discussion Evidence
12 source-linked itemsReview these external discussions before using mcp-ts-template with real data or production workflows. They are review inputs, not standalone proof that the project is production-ready.
-
01
feat(tool): flatten SDK input-validation error text and move issues to e
github / github_issue
-
02
feat(tool): first-class support for discriminated-union tool inputs (mul
github / github_issue
-
03
bug(transport): HTTP per-request McpServer cleanup leaks ~30 KB/req on h
github / github_issue
-
04
feat(linter): `schema-properties-need-type` — flag typeless leaves misse
github / github_issue
-
05
docs(api-canvas): add minimum-viable spillover server recipe as the defa
github / github_issue
-
06
feat(auth): add RFC 7662 Token Introspection as a third auth strategy
github / github_issue
-
07
feat(templates): MCPB bundle packaging for scaffolded servers
github / github_issue
-
08
Connect card: active-tab styling, default to Claude, add Codex/Cursor/Ge
github / github_issue
-
09
bug(transport): list_changed notifications silently dropped under HTTP p
github / github_issue
-
10
feat(telemetry): wire Worker-native OTel exporter (sdk-trace-web + OTLP
github / github_issue
-
11
feat(linter,docs): cross-vendor JSON Schema portability rules
github / github_issue
-
12
feat(docs/skills): codify agent-observed correctness across response des
github / github_issue
04
How to start
Only source-backed commands are shown here. Verify them in an isolated environment first.Try the prompt first
Test the workflow without installing the upstream project.
previewRead the Human Manual
Understand inputs, outputs, limits, and failure modes.
manualTake context to your AI host
Use the compiled assets in your preferred AI environment.
contextRun sandbox verification
Confirm install commands and rollback before using a primary environment.
verifynpx mcp-ts-templateOfficial start command · https://registry.modelcontextprotocol.io/v0.1/servers/io.github.cyanheads%2Fmcp-ts-template/versions/3.0.9 · verified: yes
05
Human Manual
The English page must expose the real manual, not a short placeholder.8+ sections · Human Manual
mcp-ts-template Manual
Related topics: Entrypoints and Runtime Surface, Architecture Evidence Map, Operations and Verification Boundaries
Open the full manual- https://github.com/cyanheads/mcp-ts-template Project Manual
- Table of Contents
- Repository Overview
- Related Pages
- README Evidence
- What is this?
- Selected Source Inventory
- Entrypoints and Runtime Surface
Repository Overview
Related topics: Entrypoints and Runtime Surface, Architecture Evidence Map, Operations and Verification Boundaries
Source: https://github.com/cyanheads/mcp-ts-template / Human Manual
Entrypoints and Runtime Surface
Related topics: Repository Overview, Architecture Evidence Map, Operations and Verification Boundaries
Source: https://github.com/cyanheads/mcp-ts-template / Human Manual
Architecture Evidence Map
Related topics: Repository Overview, Entrypoints and Runtime Surface, Operations and Verification Boundaries
Source: https://github.com/cyanheads/mcp-ts-template / Human Manual
Operations and Verification Boundaries
Related topics: Repository Overview, Entrypoints and Runtime Surface, Architecture Evidence Map
Source: https://github.com/cyanheads/mcp-ts-template / Human Manual
Doramagic Pitfall Log
Source-linked risks stay visible on the manual page so the preview does not read like a recommendation.
Source: Doramagic discovery, validation, and Project Pack records
06
AI Context Pack and portable assets
After deciding to continue, take the project context into your own AI host.Complete pack plus user-owned assets
These files are planning and verification assets for Claude Code, Codex, Gemini, Cursor, ChatGPT, and other AI hosts.
07
Preflight checks
Treat this page as a planning asset, not proof that your local environment is ready.- The manual is generated from source-linked project files and Doramagic validation signals.
- Community evidence warnings stay visible instead of being converted into marketing claims.
- This English page is indexable because the locale quality gate passed and explicit English index approval is enabled.
- Use the upstream repository as the final authority for installation commands, license, and version-specific behavior.
08
Pitfall Log and verification risks
Doramagic surfaces high-risk items before users treat a candidate capability as verified.Review upstream issue
The source signal needs review before production use.
Review upstream issue
The source signal needs review before production use.
Review upstream issue
The source signal needs review before production use.
Review upstream issue
Developers may expose sensitive permissions or credentials: feat(auth): add RFC 7662 Token Introspection as a third auth strategy
Review upstream issue
Developers may fail before the first successful local run: feat(templates): MCPB bundle packaging for scaffolded servers
Review upstream issue
The source signal needs review before production use.
Review upstream issue
Developers may misconfigure credentials, environment, or host setup: Connect card: active-tab styling, default to Claude, add Codex/Cursor/Gemini
Review upstream issue
Developers may misconfigure credentials, environment, or host setup: bug(utils): fetchWithTimeout attaches full upstream HTTP error body to error.data.responseBody — no cap, no MIME filter