Remote MCP server that prices software complexity and projects how AI adoption changes engineering cost over quarters.
What you can do
Calculate the cost of software complexity per feature, per quarter and per year from inputs such as vacuum effort, connascence degree, coordination hours, engineers and teams
Project how AI adoption changes that cost over coming quarters
On Pro plans, identify levers that lower the cost
Check API health without an API key
When to use it
Useful when an engineering leader or assistant wants a quick, model-based estimate of what complexity costs an organization and how AI adoption might shift that cost over time, for example to frame a discussion about refactoring or process change.
Requirements
Runs as a remote streamable HTTP endpoint; no local package. Requires an API key sent in the X-API-Key header, obtainable from the provider's account page. Pro-only fields such as levers and plan need a Pro key.
Before you install
The API key is a secret sent in the X-API-Key header. Results are model estimates: AI tool and inference spend is not included, and AI and lever values are starting values rather than fitted ones. On the Free plan, Pro fields are ignored and reported in a notice.
Connect X-API-Key credentials. They are stored privately and never shown on public pages.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.beamersaas%2Fcomplexity-cost-calculator/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Calculate what software complexity costs an engineering organization per feature, per quarter and per year, how AI adoption changes that cost over the coming quarters, and (Pro) which levers lower it.
Parametersteamsrequiredleversengineersrequiredai_adoptionhourly_rateteam_adoptionvacuum_effortrequiredai_assumptionsdecision_peopleteams_per_changefeatures_per_yearlever_assumptions+10 more
health
Health check for the Complexity Cost Calculator API. No API key required.
Takes no parameters.
Version history
2
v0.2.1LatestNov 6, 2026
v0.2.0Nov 6, 2026
Score
75%
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.