Confirm availability
Bring the operation and client you want to build. Confirm supported endpoints, schemas, versions and request limits with the team.
Developers
Build with the context your team needs.
Explore how APIs and MCP tools can connect project context to your own workflows. Discuss current availability and access with the Stark team.
Model Context Protocol
Keep tool access explicit.
An MCP integration should expose a small set of well-defined tools. Each tool needs a clear input schema, permission checks and a useful error response.
- Read project context with scoped authorization.
- Separate forecast requests from changes to work.
- Require review for consequential write actions.
1MCP connection setup231. Confirm the supported MCP client with the Stark team.42. Agree which projects and actions the client may access.53. Receive the workspace endpoint through approved onboarding.64. Store credentials in the client's secure credential storage.75. Test permissions and confirm actions require review.
Workspace endpoints and credentials are supplied through approved onboarding.
API patterns
A contract you can inspect.
The illustrative request shows how a forecast operation could accept a scope change. Production setup determines endpoint availability, authentication, scopes and limits.
Use stable identifiers, validate requests, bound retries and add idempotency keys to write operations. Keep secret credentials on your server.
Explore the developer platform1API integration setup231. Confirm endpoint availability for your workspace.42. Agree on authentication, project identifiers and scopes.53. Validate request fields and response formats.64. Handle authorization errors, retries and rate limits.75. Review forecast assumptions before using a result.
Workspace endpoints and credentials are supplied through approved onboarding.
Designing the contract
Different operations need different boundaries.
| Operation pattern | Contract to agree |
|---|---|
| Read project context | Specify the project identifier, accessible records, freshness information and behavior when a source is unavailable. |
| Request a forecast | Define the scope, units, target date and model assumptions returned with the result. |
| Propose a task | Return a draft with its source, proposed owner and unresolved fields. Keep proposal creation separate from execution. |
| Create or update work | Verify resource permissions, required review and idempotency. Return a clear operation status for repeated requests. |
A resilient integration
Make errors part of the interface.
A failed request should tell the caller what to do next. A permission rejection, an invalid resource and a temporary outage need different handling.
Agree on the actual response schema during setup. Avoid a generic success message that hides a missing source, and do not retry a write indefinitely when the result is uncertain.
Meridian · illustrative workspaceFor review
Decision brief
A forecast request worth inspecting
01
Requested context
Project identifier, current scope and the target date being discussed.
02
Returned evidence
Source timestamps, scope definition and the assumptions used for the result.
03
Failure behavior
A clear unavailable or rejected status when the operation cannot produce a valid result.
Illustrative contract guidance. Confirm production schemas, endpoints and limits before implementation.
A practical workflow
From example to an approved connection.
Review access
Choose the minimum resource and tool permissions. Agree on credential handling, the access owner and how the connection can be revoked.
Exercise the failure paths
Check invalid inputs, denied access, timeouts and repeated requests. Review successful responses against the source records before rollout.
Questions & answers
A few useful answers.
Where can I get a token?
The setup notes explain access requirements. Workspace endpoints and credentials are supplied through approved onboarding.
Can a browser store a secret API key?
Reusable secret credentials should stay out of public frontend code. Agree on authentication and credential storage appropriate to the client during setup.
Do the code examples send a request?
No. They demonstrate configuration and request patterns. The Copy control copies the visible sample for review.
Ship what you promised.
Bring the plan, the work and the next decision together.