Yaml vs MCP Ts Core
A side-by-side look at the Yaml and MCP Ts Core MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
YamlDeveloper ToolsDeclarative MCP Server Engine — define tools, resources, and prompts in mcpfusion.yaml. The docker-compose for MCP servers.49FairAuth: no auth requiredVerdict: choose Yaml for developer tools work; choose MCP Ts Core for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Yaml when
- You need dedicated capabilities in the Developer Tools domain.
- Its auth model fits you: No auth required.
Choose MCP Ts Core when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Yaml | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 49/100 · Fair | 51/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 255 | 152 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Yaml | View MCP Ts Core |
Tools & capabilities
Yaml tools
No tool names declared yet. Check the project README from the listing page.
MCP Ts Core tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Yaml
No confirmed install command for Yaml yet — follow the setup steps linked from its listing page rather than a guessed package name.
MCP Ts Core
{
"mcpServers": {
"mcp-ts-core": {
"command": "bunx",
"args": [
"@cyanheads/mcp-ts-core"
]
}
}
}
Frequently asked questions
Yaml is categorized under Developer Tools and uses an install path we have not confirmed yet. MCP Ts Core belongs to Developer Tools and uses a local stdio subprocess. Pick Yaml for developer tools work and MCP Ts Core for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Yaml has no confirmed install command yet — follow its own setup instructions.
Yaml is listed as free. Auth: no auth required. MCP Ts Core has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcpfusion-yaml and mcp-ts-core as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Yaml has a quality signal of 49/100 (Fair) with 0 views, 0 installs and 255 GitHub stars. MCP Ts Core has 51/100 (Good) with 2 views, 0 installs and 152 GitHub stars.