centrica-fieldops
Centrica publishes no MCP server. No hosted or remote server was found in the MCP registry, on npm under @modelcontextprotocol or any Centrica scope, in either Centrica GitHub organisation (github.com/Centrica has 0 public repositories; github.com/ConnectedHomes has 163, all forks or Hive app tooling and none an API contract), or on any Centrica developer surface. The FieldOps Azure APIM instance is a recent enough build to expose MCP fields in its management API — the identity-api record carries "mcpProperties": null, "a2aProperties": null and "isAgent": false — which confirms directly from Centrica's own platform that no MCP or agent surface has been configured. What follows is therefore a CANDIDATE tool list derived mechanically from the one harvested OpenAPI operation, not a published server.
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Descriptor
Candidate descriptor · transport
Tools
get_fieldops_access_token— Exchange FieldOps partner client credentials for an OAuth 2.0 bearer access token used against the Centrica FieldOps WorkOrder, Opportunity and Appointment Slots APIs.
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.