Content Tools
bokendell.com
This MCP server provides access to a personal portfolio's projects, posts, and experience timeline.
ENDPOINT 1
https://bokendell.com/mcp
MCP server metadata
- Name
- bo-kendell-portfolio
- Version
- 1.0.0
Bo Kendell's public portfolio, exposed over MCP. Tools: list_* for overviews, get_* for full detail. Resources: the same content as addressable documents — `portfolio://profile` for the summary, `portfolio://projects/{slug}` and `portfolio://writing/{slug}` for individual pieces. Prefer tools when filtering or searching, resources when you want a whole document to read or cite. All data is read-only and public — no auth required.
Known tools 8
list_projectsReturn every portfolio project (title, brief description, lifecycle, tech stack).
Inferred read-onlyget_experienceEmployment, education, projects, certifications, and awards — the full timeline.
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.bo-kendell-portfolio]
url = "https://bokendell.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"bo-kendell-portfolio": {
"type": "http",
"url": "https://bokendell.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: bo-kendell-portfolio
Remote MCP URL: https://bokendell.com/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": {
"bo-kendell-portfolio": {
"url": "https://bokendell.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"bo-kendell-portfolio": {
"type": "http",
"url": "https://bokendell.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "bo-kendell-portfolio",
"transport": "streamable-http",
"url": "https://bokendell.com/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.