INDIVIDUAL MCP TOOL

get_ai_capability

Which AI techniques he has built in production (prompting, retrieval, fine-tuning, MCP servers, local inference) and when each one is the right choice.

ashleypayne.co.uknone authenticationAvailability not checked

LIVE ENDPOINT

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

No auth detected

Connect to this endpoint to inspect the live schema for get_ai_capability and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

ashleypayne.co.uk

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.ashley-payne]
url = "https://www.ashleypayne.co.uk/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "ashley-payne": {
      "type": "http",
      "url": "https://www.ashleypayne.co.uk/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: ashley-payne
Remote MCP URL: https://www.ashleypayne.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": {
    "ashley-payne": {
      "url": "https://www.ashleypayne.co.uk/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "ashley-payne": {
      "type": "http",
      "url": "https://www.ashleypayne.co.uk/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "ashley-payne",
  "transport": "streamable-http",
  "url": "https://www.ashleypayne.co.uk/mcp"
}

MCP Inspector

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

Related tools

get_overview — Positioning, background and what makes him different from other fractional CTOs.
assess_fit — Compares a description of a project, business or problem against a fixed published rule and returns a verdict: good_fit, mixed, poor_fit or insufficient_information.
get_services — The three ways an engagement runs (Build, Partner, Consult), the fixed-price diagnostic most engagements start with, how the process works, and which client surfaces he builds: desktop applications, browser extensions, chat-platform integrations and web.
list_work — Summaries of the selected work, with the slug needed for get_case_study.
get_case_study — Full detail for one engagement: the situation, what was built, the engineering decisions and why they were made, the stack, and where there is one, the commercial outcome in indexed figures.
search_insights — Search his articles on technical leadership, fractional CTO work, AI and building SaaS.
get_insight — The complete text of one article, by slug.
get_faqs — The questions buyers ask, with his answers.