Developers / Claude Code
Bring the company into the coding conversation.
Use shared decisions, customer context, and incident history alongside the code your team is changing.
Connect an authorized client.
Configure Heidi as a remote MCP server in a compatible Claude Code installation. This example assumes an authorized token is already available in your local environment.
Use a narrowly scoped credential and review the discovered tools. Store secrets through your approved local credential process.
Authentication and scopes →claude mcp add --transport http heidi https://mcp.falkster.ai/mcp \
--header "Authorization: Bearer $HEIDI_API_TOKEN"Use context to inform the change.
Company knowledge can explain a customer commitment or historical decision. It complements repository inspection and testing. Check both the original source and the current implementation before changing behavior.
Any token savings or quality improvement should be measured on your own workload. The example below is suggested team guidance.
Before changing behavior tied to a company decision:
- Ask Heidi for relevant company context and source evidence.
- Inspect the actual repository implementation.
- Check whether the historical decision still applies.
- Review and test the proposed change before shipping.Build the next version of your company
Start with one outcome.
Think company-wide.
Bring a workflow that crosses departments. Let’s map the knowledge, controls, and evidence a meaningful rollout needs.
Discuss your rollout