Content Tools

levels.io

MCP server for searching and retrieving blog posts and tags from @levelsio's blog.

1 endpoint3 known toolsFirst detected October 12, 2026Last detected October 12, 2026

ENDPOINT 1

https://levels.io/mcp

No auth detected

Capabilities

tools

Server instructions

Read-only access to @levelsio's blog: 910 published posts. Use search_posts to find posts, then get_post for full text.

Search @levelsio's blog posts by words in the title, tags or body text, optionally filtered by tag or date.

Inferred read-only

Get one blog post in full by its slug, as markdown plus metadata.

Potential side effects

List every tag on the blog with how many posts use it.

Inferred read-only

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.levels-io-blog]
url = "https://levels.io/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "levels-io-blog": {
      "type": "http",
      "url": "https://levels.io/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: levels-io-blog
Remote MCP URL: https://levels.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": {
    "levels-io-blog": {
      "url": "https://levels.io/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "levels-io-blog": {
      "type": "http",
      "url": "https://levels.io/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "levels-io-blog",
  "transport": "streamable-http",
  "url": "https://levels.io/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.