Content Tools
monogram.io
An MCP server that exposes Monogram's website content, including company info, page markdown, blog search, and case studies, for retrieval by AI clients.
ENDPOINT 1
https://monogram.io/mcp
MCP server metadata
- Name
- monogram.io
- Version
- 1.1.0
Read-only tools for monogram.io. Start with get_site_overview for orientation, then read_page for a specific page, search_blog for published writing, list_case_studies for shipped work, and get_company_info for business identity and contact details.
Known tools 5
get_site_overviewFetch the llms.txt index of monogram.io: what Monogram does, when to engage them, and a linked map of every page.
Inferred read-onlylist_case_studiesList every published Monogram case study with its client and canonical URL, newest first.
Inferred read-onlyget_company_infoReturn Monogram's canonical business identity: legal name, description, mailing address, contact email and form, owned profiles, and the developer and llms.txt entry points.
Potential side effectsCONNECT 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.monogram-io]
url = "https://monogram.io/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"monogram-io": {
"type": "http",
"url": "https://monogram.io/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: monogram-io
Remote MCP URL: https://monogram.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": {
"monogram-io": {
"url": "https://monogram.io/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"monogram-io": {
"type": "http",
"url": "https://monogram.io/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "monogram-io",
"transport": "streamable-http",
"url": "https://monogram.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.