Context A8C via mcporter
Access Automattic work context using mcporter CLI.
Discovery
First, discover available providers and their descriptions:
mcporter list context-a8c
This returns the full tool schema including:
- Available providers (in the
providerenum) - What each provider does (in the description)
- Required and optional parameters
Read this output carefully - it tells you exactly which providers exist and when to use each one.
Two-Step Pattern
Context-a8c uses a load-then-execute pattern:
Step 1: Load Provider
mcporter call context-a8c.context-a8c-load-provider provider=<provider>
This returns the available tools for that provider and their parameters.
Step 2: Execute Tool
mcporter call 'context-a8c.context-a8c-execute-tool(provider: "linear", tool: "issue", params: {"id":"SQUARE-215"})'
Params are optional; omit params entirely for tools without arguments:
mcporter call 'context-a8c.context-a8c-execute-tool(provider: "linear", tool: "me")'
The params argument must be an object (not a JSON string). Wrap the whole call in single quotes to avoid shell parsing issues.
Workflow
- Run
mcporter list context-a8cto see available providers - Load the relevant provider to discover its tools
- Execute the specific tool with appropriate params
- Parse JSON results
End-to-End Example (Linear Issue)
mcporter list context-a8c
mcporter call context-a8c.context-a8c-load-provider provider=linear
mcporter call 'context-a8c.context-a8c-execute-tool(provider: "linear", tool: "issue", params: {"id":"SQUARE-215"})'
Common Errors
tool is a required property of input→ includetool: "<tool>"in the execute call.provider is a required property of input→ includeprovider: "<provider>"in the execute call.input[params] is not of type object→ pass an object, not a quoted JSON string.
Notes
- Always load a provider first to see exact tool names and parameters
- The
paramsargument must be valid JSON when provided - Auth is handled automatically; if it fails, direct user to
/ai/context-a8con Matticspace
微信扫一扫