Create a scoped key
Give each integration a named key with only the objects and actions it needs.
Connect Matte to the tools you use.
Use the command line for scripts and MCP for compatible AI tools. Both connect to the same live Matte workspace, with your permissions and approval rules in place.
M
One workspace, two ways to connectExample connection flow
Matte CLI
$ matte actions list
✓ Available actions returned for this key
$ matte operations get OPERATION_ID
✓ Result and status ready to inspect
MCP in a compatible AI tool
matte_actions_listSee permitted tools
Readymatte_action_preparePrepare a reviewable change
Readymatte_operation_getCheck the outcome
ReadyMatte checks access when each action runs. Changes that need approval wait for a person.
Connect with a clear path from request to result.
Discover what's available
The CLI and MCP adapter ask Matte for the actions and input fields this key can use now.
Run or prepare an action
Read directly, or prepare a change for review when the action requires approval.
Check the result
Look up the operation to see its status, warnings, and what changed.
Built for shared work.
Work from the same data.
The CLI and MCP adapter use Matte's live API, so your team and connected tools see the same workspace.
Keep permissions in place.
Matte checks the key's scope and current workspace permissions again when an action runs.
Know what happened.
Operations and runs keep results inspectable. A request being accepted is not treated as proof that the work finished.
People stay in control of sensitive changes.
The MCP adapter runs locally and does not bring its own AI model or approval authority. When an action needs human review, Matte prepares an exact proposal and waits for approval in the workspace.
Connection rules
Available toolsBased on current access
Stock or purchasing changeApproval when required
Execution resultSaved as an operation
The CLI and MCP adapter never grant themselves extra access.