Apptio MCP server: query Cloudability through a community server
Apptio's Kubernetes cost product has a first-party MCP server. Its cloud cost and portfolio products are reached through community code or their own APIs.
Checked 3 October 2026 · from The apptio, cloudability, kubecost and IBM GitHub organizations, the community server repositories, PyPI, npm and the Cloudability API endpoint
One of 91 guides to monitoring and developer tools. Each covers what an AI coding agent can get out of the tool through MCP, the protocol that lets the agent query the tool directly.
Summary
Apptio is IBM's technology spend family. It includes Cloudability for cloud cost, IBM Apptio for IT financial management and Targetprocess for strategic portfolio management.
As of 3 October 2026, Apptio has not published an MCP server for Cloudability or Targetprocess. Kubecost, which Apptio now sells, ships the official kubecost/mcp-kubecost server for Kubernetes cost.
For Cloudability, the community eelzinaty/cloudability-mcp-server wraps the v3 API in 32 tools. Several community servers also cover Targetprocess.
How Apptio works with MCP
IBM completed its acquisition of Apptio on 10 August 2023. Cloudability allocates cloud spend to teams and products through business mappings and views.
The Cloudability API lives at https://api.cloudability.com/v3. On 3 October 2026 it answered an unauthenticated request with HTTP 401 and "missing auth tokens".
On GitHub, 55 IBM repositories match a search for MCP. Adding the word cost to that search returns none, so IBM's MCP work does not reach Cloudability.
Every vendor here gets the same four checks: official, maintained, distributed and usable. Apptio passes 0 of them.
| Check | Result | Evidence |
|---|---|---|
| Official | Fail | Neither Cloudability nor Targetprocess had an Apptio-published MCP server on 3 October 2026. The apptio and cloudability GitHub organizations hold no MCP repository. Kubecost, now an Apptio product, ships kubecost/mcp-kubecost for Kubernetes cost only. |
| Maintained | Unknown | The community Cloudability server, eelzinaty/cloudability-mcp-server, was created on 15 July 2025 and last pushed on 10 June 2026. It has 4 stars. |
| Distributed | Fail | The Cloudability server installs only from its git repository with uv sync. PyPI returned 404 for cloudability-mcp-server on 3 October 2026. |
| Usable | Unknown | Every tool call needs Cloudability API credentials and an environment ID, so the tools could not be exercised without a customer account. |
| Part of the work | What Apptio has here | Can an agent reach it |
|---|---|---|
| AI cost management | Cloud spend by account, service and business mapping; budgets and forecasts | Partial. The community server's cost reports, or the REST API directly |
| Production observability | Kubernetes container cost and utilization | Partial. Kubecost's official server, or the community server's container tools |
Apptio's data answers who owns cloud spend and whether a team is over budget. It cannot tell an agent why a service slowed down or which deploy raised the bill.
What can an AI agent do with Apptio?
An agent edits or deletes a Cloudability budget
The community server registers write tools alongside its reports. remove_budget, modify_budget and remove_budget_alert change budgets for every user of the account.
It also exposes provision_kubernetes_cluster and update_cluster_configuration, which change how Cloudability collects container data.
Guard: Set your client to ask for approval before any tool whose name starts with create, modify, remove, provision or update.
The agent answers a cloud bill question from Kubecost
Kubecost's official server covers Kubernetes clusters only. Spend outside the clusters, such as managed databases or object storage, does not appear in its numbers.
Guard: Use Cloudability for the whole cloud bill and Kubecost for cost inside a cluster. State which source answered.
Every Cloudability tool call fails with an authorization error
The community server needs CLOUDABILITY_KEY_ACCESS, CLOUDABILITY_KEY_SECRET and CLOUDABILITY_ENVIRONMENT_ID. It trades the key pair for an apptio-opentoken at Apptio's Frontdoor login.
A missing environment ID raises an error even when the keys are valid.
Guard: Set all three variables, and point CLOUDABILITY_API_URL at your region's API host if you are outside the US.
How to configure Apptio MCP for agents
- 1
Approve writes
The community server can delete budgets and change cluster provisioning, so keep its write tools behind client approval.
- 2
Region
The default API host is the US one. EU, APAC and ME accounts need their own
CLOUDABILITY_API_URL. - 3
Default view
CLOUDABILITY_DEFAULT_VIEW_IDsets the Cloudability view that reports use when the agent names none.
Paste this into your agent’s instructions
When you answer from Cloudability data, state: - The view, the date range and the cost measure used. - The cost measure's name exactly as Cloudability returns it. Never create, modify or remove a budget without explicit approval. Say when a figure comes from Kubecost rather than Cloudability.
Do you need the MCP server at all?
Kubecost. kubecost/mcp-kubecost is first-party, Apache-2.0 licensed and was pushed on 2 October 2026. Its 11 read-only tools cover Kubernetes allocation and savings.
The Cloudability REST API. An agent with an HTTP tool can call /v3/reporting/cost/run or /v3/budgets directly, using the same token the community server obtains.
Other cloud cost servers. Vantage, CloudZero and AWS Cost Explorer each publish first-party servers over provider billing. None of them reads Apptio's business mappings.
Targetprocess. Community servers include SerhiiMaksymiv/targetprocess-mcp-server (7 stars, pushed 14 September 2026) and msbritt/apptio-targetprocess-mcp (0 stars, pushed 18 May 2026).
Use Kubecost's server for cluster cost. Use the Cloudability API, or the community server with writes gated, when the question needs Apptio's allocation.
Apptio integration setup
Cloudability has no hosted MCP endpoint. Run the community server locally from a clone, or call the REST API from the agent.
Community Cloudability server in Claude Code
Clone eelzinaty/cloudability-mcp-server and run uv sync first. It requires Python 3.14 or later.
claude mcp add-json "cloudability" '{"command":"uv",
"args":["--directory","/path/to/cloudability-mcp-server",
"run","python","main.py"],
"env":{"CLOUDABILITY_ENVIRONMENT_ID":"<env-id>",
"CLOUDABILITY_KEY_ACCESS":"<key-access>",
"CLOUDABILITY_KEY_SECRET":"<key-secret>"}}'Kubecost for cluster cost
Kubecost's server is bundled with its Helm install. It starts from one variable, KUBECOST_BASE_URL, pointing at your Kubecost instance.
Every other client
Each block below is the configuration for one client, with the file path and the key that client expects.
Calling the Cloudability API without MCP
The community server's code shows the token flow: post the key pair to Frontdoor, then send the returned apptio-opentoken with your environment ID.
The request below lists budgets once you hold a token.
curl -s https://api.cloudability.com/v3/budgets \ -H "apptio-opentoken: $APPTIO_TOKEN" \ -H "apptio-environmentid: $CLOUDABILITY_ENV_ID"
What engineers report
Community interest is spread thin. The Cloudability server has 4 stars and 5 forks. A GitHub search for Targetprocess MCP servers returns 12 repositories, the largest with 7 stars.
Should you connect an agent to Apptio?
Yes for Kubecost, which has an official server. For Cloudability, only after reviewing the community server and gating its write tools. Best for FinOps teams already on Cloudability who want an agent to read cost reports and budgets.
- Strongest fit
- Yes for Kubecost, which has an official server. For Cloudability, only after reviewing the community server and gating its write tools.
- Main advantage
- Cloudability's allocation joins cloud bills to teams, which provider billing servers cannot do.
- Main weakness
- No Apptio-published server covers Cloudability, IBM Apptio or Targetprocess.
- Operational risk
- The community Cloudability server can delete budgets and alerts if its key allows writes.
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.
See agent observabilityFrequently asked questions
Does Apptio have an MCP server?
Only for Kubecost, which Apptio now sells. As of 3 October 2026, Apptio has not published one for Cloudability or Targetprocess.
Is there a Cloudability MCP server?
Yes, a community one. eelzinaty/cloudability-mcp-server wraps the Cloudability v3 API in 32 tools and installs from git.
Does IBM publish one, since it owns Apptio?
No. Of the 55 IBM GitHub repositories that match MCP, none matches cost as well.
Can the community server change data in Cloudability?
Yes. It includes tools to create, modify and remove budgets and budget alerts, and to provision Kubernetes clusters.
