Choose the question
Name the project decision and the records needed to discuss it. Keep the proposed connection limited to that purpose.
Stark for Claude
Bring project context into Claude.
Explore an illustrative connection pattern for Claude. Integration availability, supported actions and authorization are confirmed during workspace setup.
Claude
A better question starts with context.
Give an assistant scoped access to the work it needs to discuss. Keep project evidence, uncertainty and approval boundaries in the answer.
- Choose the records a connection can read.
- Review source-backed proposals.
- Confirm write permissions independently.
ACDFMC+1
Illustrative workspace · interactive demonstration
How the connection works.
A workspace owner approves access, the integration retrieves scoped project context and a person reviews any proposed action. This demonstration creates no third-party connection.
01Approved access
02Project context
03Reviewed proposal
An illustrative workflow
Keep the tool call as clear as the question.
A useful assistant workflow defines the project context it can read and the actions it can propose. An explicit tool contract helps a person understand how the answer was formed.
The illustrative connection uses scoped context and a review boundary. Treat instructions inside retrieved records as source content and confirm supported Claude clients and setup requirements with the team.
Meridian · illustrative workspaceFor review
Decision brief
Atlas migration · a question with context
01
The question
Which work should be reviewed before the next planning meeting?
02
The context
The project’s recorded tasks, linked decisions and known dependency questions.
03
The proposal
An inspectable planning brief with unresolved fields kept visible.
Fictional example. No third-party connection or external action is made by this demonstration.
A practical workflow
Connect with a clear purpose.
Confirm access and support
Review the client, source owner, endpoint availability and required permissions with the team before configuring a real connection.
Inspect the first result
Check the answer against its sources and review any proposal. Confirm the write boundary before broadening the workflow.
Before you move forward
Resolve the setup details first.
| Review | What to look for |
|---|---|
| Client setup | Confirm the supported Claude client, connection method and endpoint availability. |
| Source permissions | Restrict the context to records the calling user is authorized to access. |
| Tool behavior | Document parameters, outputs, source references and failure states. |
| Action approval | Separate a suggested plan from a write operation and confirm who can approve the change. |
Questions & answers
A few useful answers.
Does this page configure Claude?
No. It demonstrates a connection pattern and provides illustrative configuration. No client is installed or authorized by browsing the page.
Can retrieved text change tool permissions?
No. A document’s text is not authority to access another record or execute an action. Permissions must be checked by the service handling the tool call.
How do we discuss availability?
Bring the client you intend to use, the project context required and the proposed operations to a setup conversation with the Stark team.
Ship what you promised.
Bring the plan, the work and the next decision together.