General Tools
enso.bot
Fetches structured company information, experiments, blog posts, and career listings for enso.
ENDPOINT 1
https://www.enso.bot/mcp
MCP server metadata
- Name
- enso-mcp
- Version
- 0.1.0
Public tools for enso.bot - the agentic growth lab. Use these to look up enso's Agentic Lab experiments (platform-attention growth hack blog posts), published blog posts, open roles, and company/product overview. All content is public.
Known tools 6
get_company_infoFetch a structured overview of enso: what the company does, its five agent surfaces, how engagements are scoped, founding team, and key URLs.
Inferred read-onlylist_experimentsList enso's Agentic Lab experiments (platform-attention growth hack blog posts).
Inferred read-onlylist_blog_postsList enso's published blog posts (blog posts on platform-attention experiments).
Inferred read-onlyget_careerFetch the full description for a single enso open role by slug, including summary, responsibilities, signals and bonus criteria.
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.enso-mcp]
url = "https://www.enso.bot/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"enso-mcp": {
"type": "http",
"url": "https://www.enso.bot/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: enso-mcp
Remote MCP URL: https://www.enso.bot/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": {
"enso-mcp": {
"url": "https://www.enso.bot/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"enso-mcp": {
"type": "http",
"url": "https://www.enso.bot/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "enso-mcp",
"transport": "streamable-http",
"url": "https://www.enso.bot/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for enso.bot was fetched 2026-08-01T08:07:26.018Z and is being refreshed.
enso.bot is assessed as Trusted: Domain has an established technology history spanning over a year.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.