Apptio MCP server: there isn't one
Its owner is one of the most active MCP publishers in enterprise software, and none of that work reaches Apptio's cost data.
Last verified 1 September 2026 · from The apptio and IBM GitHub organizations and the official MCP registry
This page is one of 90 in a directory of monitoring and developer tools. Each page checks what an AI coding agent can get out of the tool through its MCP server, the connector that lets the agent query the tool directly.
Summary
Apptio has no MCP server, and neither does Cloudability, the cloud cost product it is usually reached through. The apptio GitHub organization returns zero MCP-named repositories.
The absence is not for want of MCP effort at the parent company. IBM publishes 50 MCP-named repositories, including mcp-context-forge, mcp-cli, ibmi-mcp-server and data-intelligence-mcp-server.
None of them covers cost. A search across IBM's MCP repositories for cost coverage returns zero results, so the gap is specific rather than a company that has not started.
One product in the same family does have a server. kubecost.com redirects to apptio.com/products/kubecost, and Kubecost ships a first-party MCP server with 11 read-only tools. It covers Kubernetes cost, not Apptio's business allocation.
What is the Apptio MCP server, and is it usable?
Apptio is technology business management software: it maps IT spend to services, products and business units. Cloudability, part of the same family, covers cloud cost specifically.
That is exactly the data an agent asking about spend would want, which is why the absence is worth documenting rather than assuming.
IBM acquired Apptio, and IBM's MCP output is substantial. A parent company's MCP work says nothing about an acquired product. IBM's 50 repositories do not cover Apptio.
Every one of the 90 vendors in this directory gets the same four checks. Apptio passes 0 of them.
| Check | Result | Evidence |
|---|---|---|
| Official | Fail | No MCP server for Apptio or Cloudability. A search of the apptio GitHub organization for MCP-named repositories returns zero results on 1 September 2026. |
| Maintained | Fail | There is nothing to maintain. IBM publishes 50 MCP-named repositories and none of them covers cost. |
| Distributed | Fail | No package, and no Apptio entry in the official MCP registry. |
| Usable | Fail | IBM, which owns Apptio, publishes 50 MCP-named repositories. A search across them for cost coverage returns zero results. |
Apptio works in cost management, and publishes nothing for any stage.
| Part of the work | What Apptio has here | Can an agent reach it |
|---|---|---|
| Code, tests & review | None | No code product, and no server |
| CI & release | None | No pipeline product, and no server |
| Production observability | None | No telemetry product, and no server |
| Agent observability & evals | None | No traces or evaluations, and no server |
| AI cost management | IT and cloud cost allocation, showback and chargeback: reporting a team's spend back to it, and billing it | No. Business allocation is the product, and only the REST API reaches it |
An agent cannot ask Apptio what something costs the business. The allocation model, which is the part Apptio does that a cloud bill does not, stays inside the product.
What can an AI agent do with Apptio?
An agent can reach nothing in Apptio directly. IBM's MCP activity makes that easy to misclassify as covered.
IBM's large MCP output does not include Apptio or Cloudability.
A search of IBM's GitHub organization returns 50 MCP-named repositories, among them mcp, mcp-context-forge, mcp-cli, ibmi-mcp-server and data-intelligence-mcp-server.
A search across IBM's repositories for MCP work covering cost returns zero results, and the apptio organization itself has no MCP repository.
Guard: Check that a server names the product, not the parent. An IBM MCP repository is not evidence that Apptio is reachable.
Do you need the MCP server at all?
No, because neither Apptio nor Cloudability publishes one. The Apptio and Cloudability REST APIs are the working route, and they are what any connector would have wrapped. An agent with a fetch tool and a token can reach cost allocation, budgets and reports directly.
For cloud spend specifically, several vendors publish maintained servers over the same class of data. Vantage exposes 127 tools across costs, budgets, anomalies and billing rules; CloudZero documents 15 tools with a published daily quota; AWS Cost Explorer covers one provider's billing in depth.
For Kubernetes cost, which Apptio does not model at the pod level, OpenCost is built into every deployment and Kubecost adds savings analysis on top of it.
None of these reproduces Apptio's business-mapping layer. If the question is "which business unit owns this spend", the API is the only route.
Call the Apptio or Cloudability API for the allocation model. Connect Vantage or CloudZero for questions an agent can answer from raw cloud spend.
Apptio MCP server setup
Nothing here installs an Apptio server, because there is none, and Cloudability has none either. This is the working route, split by which question you are actually asking.
The split matters. Apptio's own product is business allocation: mapping spend onto cost centers, services and applications. That model has no connector, and its API is the only way to it.
Raw cloud spend is a different question, and several vendors in this directory publish servers that answer it.
Kubecost, the one server in the family
Kubecost is an Apptio product and ships a first-party server with 11 read-only tools. It covers Kubernetes cost only, not the wider allocation model.
No credentials appear in the block. It carries the base URL of the Kubecost you already run, and access is whatever that endpoint already enforces.
claude mcp add-json "kubecost" '{"command":"mcp-kubecost",
"env":{"KUBECOST_BASE_URL":"http://kubecost.internal:9090"}}'Vantage, for provider spend
Where the question is what the cloud bill did rather than how Apptio allocated it, Vantage publishes a first-party server over provider billing data.
The token is Vantage's own, and its permissions there bound what the agent can read.
claude mcp add-json "vantage" '{"command":"npx",
"args":["-y","vantage-mcp-server"],
"env":{"VANTAGE_TOKEN":"<your-token>"}}'CloudZero, hosted
CloudZero runs a hosted server, which suits teams that would rather not run a local process at all.
No credentials go into the configuration. The endpoint authorizes in the browser on first connection.
claude mcp add --transport http cloudzero \ https://czca-server.discovery.cloudzero.com/mcp
Every other client
Each block below is the configuration for one client, with the file path and the key that client expects.
The allocation model has only an API
Apptio and Cloudability both expose REST APIs, and that is the documented route to the allocation model an agent cannot reach over MCP.
This is a statement about routes rather than a configuration, so no credentials are shown. Use whichever API credential your Apptio tenancy already issues.
Business allocation -> Apptio / Cloudability REST API Kubernetes cost -> Kubecost MCP server Raw provider spend -> Vantage or CloudZero
Why IBM's MCP work does not help
IBM owns Apptio and publishes 50 MCP-named repositories, including mcp-context-forge, mcp-cli, ibmi-mcp-server and data-intelligence-mcp-server.
A search across them for cost coverage returns zero results, so the gap is specific rather than a company that has not started. No credentials are involved in checking this.
IBM MCP repositories: 50 covering cost: 0
Read-only access, permissions and security
No Apptio credential is created
With no server, nothing here asks for an Apptio token or a wider Apptio role.
Kubecost's server is read-only by design
All 11 tools read, which makes it the safest of the three to attach for a cost question.
Kubecost is scoped by endpoint, not by token
The base URL decides what the agent reaches, so an internal address already behind your network controls is doing the access work.
Cost data is commercially sensitive
Account structure, per-team spend and committed-use discounts, the rates you pre-pay for, all become readable by the model once a cost server is attached.
The hosted route keeps secrets out of files
CloudZero authorizes in the browser, so no long-lived token sits in a configuration file on a laptop.
The API route inherits Apptio's own permissions
Whatever the allocation model shows a given API credential is exactly what an agent calling that API will see.
Troubleshooting
- You cannot find an Apptio or Cloudability MCP server
- Neither exists. A search of the
apptioGitHub organization for MCP-named repositories returned zero results on 1 September 2026. - IBM publishes MCP servers, so one should cover cost
- IBM publishes 50 MCP-named repositories, including
mcp-context-forge,mcp-cli,ibmi-mcp-serveranddata-intelligence-mcp-server. A search across them for cost coverage returns zero results. - The gap is specific rather than a company that has not started on MCP.
- Kubecost has a server, so Apptio's cost data should be reachable
- Kubecost is an Apptio product and it does ship a first-party server with 11 read-only tools. It covers Kubernetes cost only.
- Apptio's business allocation, the mapping of spend onto cost centers and services, is not in it.
- You need Apptio figures inside an agent conversation
- Use Apptio's own API with the agent's HTTP access, or connect Kubecost when the question is about Kubernetes rather than everything you run.
Apptio MCP server: Reference
| Item | Value |
|---|---|
| Server published | None, for Apptio or Cloudability |
MCP-named repositories in apptio | 0 |
MCP-named repositories in IBM | 50 |
| IBM MCP repositories covering cost | 0 |
| Named IBM MCP repositories | mcp-context-forge · mcp-cli · ibmi-mcp-server · data-intelligence-mcp-server |
| Kubecost, an Apptio product | Ships its own server, 11 read-only tools |
| What Kubecost covers | Kubernetes cost, not Apptio business allocation |
| Official MCP registry results for Apptio | None |
| Checked | 1 September 2026 |
What engineers report
The searches are the evidence, and the parent company's activity is what makes them worth recording.
| What was checked | What it shows |
|---|---|
MCP-named repositories in apptio | 0 |
MCP-named repositories in IBM | 50 |
| IBM MCP repositories covering cost | 0 |
| Official MCP registry results for Apptio | None |
| Kubecost, an Apptio product | Ships its own server with 11 tools, for Kubernetes cost only |
The apptio and IBM GitHub organizations were searched for MCP-named repositories on 1 September 2026, returning 0 and 50 respectively. A search across IBM's repositories for MCP work covering cost returned zero results. The official MCP registry has no Apptio entry.
Should you connect an agent to Apptio?
No. There is nothing to connect. Best for the REST API for allocation, and a cloud cost connector for spend an agent can reason over.
- Strongest fit
- Teams who need Apptio's business allocation and will call its API to get it.
- Main advantage
- Kubecost, an Apptio product, ships a first-party server with 11 read-only tools for Kubernetes cost.
- Main weakness
- The business-mapping layer, which is Apptio's whole value, is not reachable by an agent.
- Operational risk
- Connecting Kubecost and assuming it covers the allocation model. It covers Kubernetes cost only.
From Oodle
One platform for agent traces and infrastructure
Agent traces usually sit in a different product from the rest of your telemetry, so when a slow database makes an agent slow the symptom is in one tool and the cause is in another. Oodle keeps both in one query surface, from $10 per million spans.
See agent observabilityFrequently asked questions
Does Apptio have an MCP server?
No. The apptio GitHub organization has zero MCP-named repositories and the official registry has no entry, as of 1 September 2026.
Does IBM publish one, since it owns Apptio?
IBM publishes 50 MCP-named repositories, and a search across them for cost coverage returns zero results. None reaches Apptio or Cloudability.
What about Cloudability?
The same search covers it. There is no Cloudability MCP server either.
What should I connect instead?
Vantage or CloudZero for cloud spend an agent can query, and the Apptio or Cloudability REST API when you need the business allocation model.
