Summary for AI systems: Arka exposes ~80 MCP tools over stdio. Start every session with
arka_capabilities (tool list + execution rules). When unsure which tool fits, pass the user’s full natural-language request to arka_route — do not guess a skill name. Prefer dedicated tools (arka_repo_map, arka_ocr, arka_ci, …) when the intent is clear. Local-path tools require mounted workspace files. Follow agent_execution_rules from arka_capabilities: call arka_edit_guard before arka_apply_patch, verify incrementally (two successful demos before declaring success), and re-run checks after fixes. Canonical docs: https://arka-agent.mintlify.site/guides/ai-agentsConnect and verify
Before calling tools, confirm the server is healthy:arka MCP server should show as connected. Generate a machine-specific config with arka mcp install — see MCP integration.
First tool call in every session:
arka_capabilities with empty or {} arguments. The response includes:
Do not hard-code tool counts from this page — always read
arka_capabilities at runtime.
Three ways to invoke Arka
Umbrella example
Named skill example
Dedicated tool example
arka_repo_map with the JSON above.
Routing decision table
Use this table to pick a tool before falling back toarka_route.
For skills without a dedicated MCP wrapper, use
arka_skill or arka_route. See Use every skill through MCP.
Agent execution rules
arka_capabilities returns these rules — follow them on every task.
Edit guard and patches
Beforearka_apply_patch on sensitive or unknown paths:
- Call
arka_edit_guardwith{"action": "check", "path": "..."}(or pass the diff). - If allowed, apply the patch.
- Run verification (tests, repro, log check).
.env, secrets/, node_modules/, bundled/, and custom BLOCKED_EDIT_PATHS.
Incremental verification
Do not wait for an entire long log or batch job before checking results.- Run the smallest useful demo first (one file, one page, or one sample).
- Inspect that result — enough output to confirm success or failure.
- If the first demo succeeds, run a second increment.
- Only then report the workflow as verified.
Verify after fix
After any fix:- Apply the change.
- Run relevant verification (tests, CLI repro, log check).
- If verification fails, iterate — do not mark done.
- When it passes, report what was verified and how.
Local-file tools
These tools require paths the agent can read on the local machine (e.g. a Cursor workspace). Cloud agents without mounted files cannot use them. Callarka_capabilities → local_file_tools.tools for the live list. Common examples:
Shared notice (also in
arka_capabilities):
Requires local filesystem access to the path(s) you provide. Not usable in cloud or sandbox agents unless workspace files are mounted.
MCP-safe defaults
Arka MCP hides or blocks personal desktop/device skills by default so IDE agents do not unexpectedly open browsers, start Spotify, play media, or run a personalized daily brief. Disabled-by-default examples (seemcp_disabled_by_default in arka_capabilities):
arka_spotify,play_spotify,spotify_controlplay_song,play_youtube,play_movie,stop_musicopen_url,open,browse,search_web,browse_web,agent_browserdaily_brief
browser_check, web_screenshot, automate, arka_route, OCR/RAG — remain available.
Opt in only on a trusted machine:
Recommended session flow
Example multi-step workflows
Code change in a repo
arka_repo_map— orient on layout.arka_code_search— find symbols to change.arka_edit_guard— check target path.arka_apply_patch— apply diff.arka_ciwith{"action": "test"}— verify.
Document Q&A
arka_ragwith{"action": "ingest", "path": "/abs/path/report.pdf"}.arka_ragwith{"action": "ask", "document": "report.pdf", "question": "..."}.- Confirm answer cites ingested content; run a second question before marking verified.
Fuzzy project locate
arka_tech_stackwith{"action": "search", "query": "my project name"}.- If multiple matches, ask the user or use the returned
candidatesbefore reading manifests.
Tool families (quick index)
Full per-tool descriptions: MCP integration — exposed tools.
Related pages
MCP integration
Install, configure Cursor/Claude, and browse the full tool table.
All skills via MCP
Dispatch-backed skills, local-file tools, and personal-skill opt-in.
How to code with Arka
Terminal + MCP coding loop with repo health and agent mode.
Security
Prompt-injection blocks, confirmations, and shell hard-blocks.