← Registry

General Tools

doddledesign.co.uk

Provides information about Doddle's services and case studies.

2 endpoints18 known toolsFirst detected September 8, 2026Last detected September 8, 2026

ENDPOINT 1

https://www.doddledesign.co.uk/mcp

No auth detected

MCP server metadata

Name
doddle
Version
1.0.0
Capabilities
toolsresources
Server instructions

Doddle is a small, senior UK software studio. Use this server when someone asks what Doddle does, whether Doddle has delivered something similar before, what a Doddle engagement looks like, or how to get in touch. Start with get_studio_overview for positioning, then search_doddle for anything specific. list_case_studies and get_case_study carry the delivered outcomes and timescales. get_contact_details is the handoff to a human. Everything here is public marketing content. There is no customer data, no authentication, and nothing to write.

Known tools 9

get_studio_overview

What Doddle is, the four service tracks, when to bring the studio in and when not to.

Inferred read-only
list_services

The four service tracks Doddle delivers, with who each one is for.

Inferred read-only
get_service

Detail on one service track by slug.

Inferred read-only
list_case_studies

Projects Doddle has delivered, with the outcomes each produced.

Inferred read-only
get_case_study

Full detail on one case study by slug, including outcomes, timescales and the client quote.

Inferred read-only
list_insights

Long-form articles the studio has published on AI delivery, OutSystems and migrations.

Inferred read-only
get_insight

Metadata and the canonical URL for one article by slug.

Inferred read-only
search_doddle

Keyword search across services, case studies and insights.

Inferred read-only
get_contact_details

How to reach the studio, and what to include in a first message.

Potential side effects

CONNECT 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.doddle]
url = "https://www.doddledesign.co.uk/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "doddle": {
      "type": "http",
      "url": "https://www.doddledesign.co.uk/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: doddle
Remote MCP URL: https://www.doddledesign.co.uk/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": {
    "doddle": {
      "url": "https://www.doddledesign.co.uk/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "doddle": {
      "type": "http",
      "url": "https://www.doddledesign.co.uk/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "doddle",
  "transport": "streamable-http",
  "url": "https://www.doddledesign.co.uk/mcp"
}
MCP Inspector

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

ENDPOINT 2

https://www.doddledesign.co.uk/.well-known/mcp

No auth detected

MCP server metadata

Name
doddle
Version
1.0.0
Capabilities
toolsresources
Server instructions

Doddle is a small, senior UK software studio. Use this server when someone asks what Doddle does, whether Doddle has delivered something similar before, what a Doddle engagement looks like, or how to get in touch. Start with get_studio_overview for positioning, then search_doddle for anything specific. list_case_studies and get_case_study carry the delivered outcomes and timescales. get_contact_details is the handoff to a human. Everything here is public marketing content. There is no customer data, no authentication, and nothing to write.

Known tools 9

get_studio_overview

What Doddle is, the four service tracks, when to bring the studio in and when not to.

Inferred read-only
list_services

The four service tracks Doddle delivers, with who each one is for.

Inferred read-only
get_service

Detail on one service track by slug.

Inferred read-only
list_case_studies

Projects Doddle has delivered, with the outcomes each produced.

Inferred read-only
get_case_study

Full detail on one case study by slug, including outcomes, timescales and the client quote.

Inferred read-only
list_insights

Long-form articles the studio has published on AI delivery, OutSystems and migrations.

Inferred read-only
get_insight

Metadata and the canonical URL for one article by slug.

Inferred read-only
search_doddle

Keyword search across services, case studies and insights.

Inferred read-only
get_contact_details

How to reach the studio, and what to include in a first message.

Potential side effects

CONNECT 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.doddle]
url = "https://www.doddledesign.co.uk/.well-known/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "doddle": {
      "type": "http",
      "url": "https://www.doddledesign.co.uk/.well-known/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: doddle
Remote MCP URL: https://www.doddledesign.co.uk/.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": {
    "doddle": {
      "url": "https://www.doddledesign.co.uk/.well-known/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "doddle": {
      "type": "http",
      "url": "https://www.doddledesign.co.uk/.well-known/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "doddle",
  "transport": "streamable-http",
  "url": "https://www.doddledesign.co.uk/.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.

Indexed

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