Content Tools
rye.dev
Provides access to blog posts and projects via search and retrieval operations.
ENDPOINT 1
https://rye.dev/mcp
MCP server metadata
- Name
- rye.dev
- Version
- 1.3.0
Known tools 12
search_siteSemantic (vector similarity) search across blog posts and projects — the same Cloudflare Vectorize retrieval the Ask chatbot uses, without the LLM call.
Inferred read-onlylist_projectsReturn all portfolio projects with their slug, title, and short description.
Inferred read-onlyget_nowReturn what Cameron is currently working on, learning, building, reading, and up to in life — the live /now page sections.
Inferred read-onlyget_readingReturn Cameron's reading list — books currently reading, finished, or abandoned, with notes.
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.rye-dev]
url = "https://rye.dev/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"rye-dev": {
"type": "http",
"url": "https://rye.dev/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: rye-dev
Remote MCP URL: https://rye.dev/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": {
"rye-dev": {
"url": "https://rye.dev/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"rye-dev": {
"type": "http",
"url": "https://rye.dev/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "rye-dev",
"transport": "streamable-http",
"url": "https://rye.dev/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 rye.dev was fetched 2026-08-16T09:36:20.018Z and is being refreshed.
rye.dev 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.