Developer Tools
expanso.io
An MCP server that provides Expanso documentation search/retrieval and tools to validate and inspect pipeline YAML configurations and component schemas.
ENDPOINT 1
https://mcp.expanso.io/mcp
MCP server metadata
- Name
- expanso-mcp-server
- Version
- 1.0.0
Known tools 10
get_component_schemaGet the schema for an Expanso pipeline component including field definitions, types, defaults, and examples.
Inferred read-onlyget_bloblang_referenceGet Bloblang function and method reference for writing data transformations.
Inferred read-onlysuggest_pipeline_patternGet pipeline pattern suggestions based on a natural language use case description.
Inferred read-onlyexplain_errorGet detailed explanation and fix suggestions for a pipeline validation or runtime error.
Inferred read-onlylist_componentsList available Expanso pipeline components with filtering by category, tag, or search term.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.expanso-mcp-server]
url = "https://mcp.expanso.io/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"expanso-mcp-server": {
"type": "http",
"url": "https://mcp.expanso.io/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: expanso-mcp-server
Remote MCP URL: https://mcp.expanso.io/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"expanso-mcp-server": {
"url": "https://mcp.expanso.io/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"expanso-mcp-server": {
"type": "http",
"url": "https://mcp.expanso.io/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "expanso-mcp-server",
"transport": "streamable-http",
"url": "https://mcp.expanso.io/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.