General Tools
robustdevs.co
Provides general-purpose tools through the Model Context Protocol.
ENDPOINT 1
https://robustdevs.co/api/mcp
MCP server metadata
- Name
- robust-devs
- Version
- 1.0.0
Read-only access to Robust Devs content, pricing and capabilities. Every tool is safe to call; none of them write.
Known tools 4
list_blog_postsList published Robust Devs articles about custom software and AI development, newest first.
Inferred read-onlylist_case_studiesList published Robust Devs client case studies, newest first, including outcome metrics, tech stack and engagement length where the client permitted publication.
Inferred read-onlyget_pricingReturn the Robust Devs pricing model: the one standing published price, what it includes, and how everything else is scoped.
Inferred read-onlyget_capabilitiesReturn what Robust Devs can be engaged to build, where its shipped work is deepest, and how to start an engagement.
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.robust-devs]
url = "https://robustdevs.co/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"robust-devs": {
"type": "http",
"url": "https://robustdevs.co/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: robust-devs
Remote MCP URL: https://robustdevs.co/api/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": {
"robust-devs": {
"url": "https://robustdevs.co/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"robust-devs": {
"type": "http",
"url": "https://robustdevs.co/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "robust-devs",
"transport": "streamable-http",
"url": "https://robustdevs.co/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
ENDPOINT 2
https://robustdevs.co/mcp
MCP server metadata
- Name
- robust-devs
- Version
- 1.0.0
Read-only access to Robust Devs content, pricing and capabilities. Every tool is safe to call; none of them write.
Known tools 4
list_blog_postsList published Robust Devs articles about custom software and AI development, newest first.
Inferred read-onlylist_case_studiesList published Robust Devs client case studies, newest first, including outcome metrics, tech stack and engagement length where the client permitted publication.
Inferred read-onlyget_pricingReturn the Robust Devs pricing model: the one standing published price, what it includes, and how everything else is scoped.
Inferred read-onlyget_capabilitiesReturn what Robust Devs can be engaged to build, where its shipped work is deepest, and how to start an engagement.
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.robust-devs]
url = "https://robustdevs.co/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"robust-devs": {
"type": "http",
"url": "https://robustdevs.co/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: robust-devs
Remote MCP URL: https://robustdevs.co/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": {
"robust-devs": {
"url": "https://robustdevs.co/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"robust-devs": {
"type": "http",
"url": "https://robustdevs.co/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "robust-devs",
"transport": "streamable-http",
"url": "https://robustdevs.co/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
ENDPOINT 3
https://robustdevs.co/.well-known/mcp
MCP server metadata
- Name
- robust-devs
- Version
- 1.0.0
Read-only access to Robust Devs content, pricing and capabilities. Every tool is safe to call; none of them write.
Known tools 4
list_blog_postsList published Robust Devs articles about custom software and AI development, newest first.
Inferred read-onlylist_case_studiesList published Robust Devs client case studies, newest first, including outcome metrics, tech stack and engagement length where the client permitted publication.
Inferred read-onlyget_pricingReturn the Robust Devs pricing model: the one standing published price, what it includes, and how everything else is scoped.
Inferred read-onlyget_capabilitiesReturn what Robust Devs can be engaged to build, where its shipped work is deepest, and how to start an engagement.
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.robust-devs]
url = "https://robustdevs.co/.well-known/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"robust-devs": {
"type": "http",
"url": "https://robustdevs.co/.well-known/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: robust-devs
Remote MCP URL: https://robustdevs.co/.well-known/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": {
"robust-devs": {
"url": "https://robustdevs.co/.well-known/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"robust-devs": {
"type": "http",
"url": "https://robustdevs.co/.well-known/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "robust-devs",
"transport": "streamable-http",
"url": "https://robustdevs.co/.well-known/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.