cosmos-setup
CommandSet up the optional Azure Cosmos DB MCP Toolkit connection for live database operations
/cosmos-setupWhat it tells Claude to do
39 linesThe prompt this command injects, verbatim. Worth reading before you run it.
# Cosmos DB MCP Setup
Help the user configure the optional Azure Cosmos DB MCP Toolkit connection.
This enables live database operations (queries, schema discovery, vector search)
but is not required — the plugin's skills, agent, and commands work without it.
For detailed instructions, see [SETUP.md](../SETUP.md).
## Steps
1. **Check prerequisites:**
- Ask if they have an Azure Cosmos DB account. If not, direct them to: https://learn.microsoft.com/azure/cosmos-db/nosql/quickstart-portal
- Ask if they have deployed the MCP Toolkit. If not, direct them to: https://github.com/AzureCosmosDB/MCPToolKit#quick-start
2. **Get connection details:**
- Ask for their deployed MCP Toolkit URL (from `deployment-info.json` in the MCPToolKit output)
- Ask for their Entra App Client ID (also from `deployment-info.json`)
- Help them get a JWT token by running:
```
az login
az account get-access-token --resource "YOUR-ENTRA-APP-CLIENT-ID" --query accessToken -o tsv
```
- The `--resource` value is the Entra App Client ID from the MCPToolKit deployment output
3. **Set environment variables:**
- Guide them to set `COSMOSDB_MCP_SERVER_URL` to their toolkit URL
- Guide them to set `COSMOSDB_MCP_JWT_TOKEN` to their JWT token
- Note: JWT tokens expire after ~1 hour and need to be refreshed
4. **Create MCP config:**
- Guide them to copy `.mcp.example.json` to `.mcp.json` in their project root
- The config references the environment variables set above
5. **Verify connection:**
- Restart Claude Code after adding `.mcp.json`
- Try listing databases using the MCP tools
- If connection fails, refer to troubleshooting in [SETUP.md](../SETUP.md)
$ARGUMENTSShipped by 1 plugin
Installing any of these installs this command.
What this can do
Capabilities declared in this component's own frontmatter — not inferred.
Inherit all session tools
Declares no tool restrictions — inherits every session tool
~22 tokens of context used while enabled, before you invoke anything
Reviews
Log in to leave a review.
No reviews yet — be the first.
Explore related
Other things in this space — across every part of the ecosystem, not just commands.
Commandssimilar to this one
All commands →altimate
Delegate a task to altimate-code, the specialised data-engineering CLI agent (warehouse access, column-level lineage, cross-DB, FinOps, query optimization)
windsor-types
Generate TypeScript type definitions for a Windsor.ai connector's data schema
design-survey
Interactive design session for a new survey — research goal, audience, hypotheses, questions, modality, output schema
Plugins
All plugins →receipts
A personal Claude Code impact report for justifying your usage to a manager or a self-review: what you shipped, which projects it went to, and each project's share of your usage. Reads your ~/.claude/projects transcripts and runs read-only git locally; only counts and project names are sent to write
32.8K stars
atomic-agents
Comprehensive development workflow for building AI agents with the Atomic Agents framework. Includes specialized agents for schema design, architecture planning, code review, and tool development. Features guided workflows, progressive-disclosure skills, and best practice validation.
6.1K stars
databases-on-aws
Expert database guidance for the AWS database portfolio. Design schemas, execute queries, handle migrations, and choose the right database for your workload.
844 stars
Skills
All skills →create-atomic-tool
Build a `BaseTool[InSchema, OutSchema]` subclass — input/output schemas, `BaseToolConfig`, `run()` (and optional `run_async()`), env-driven secrets, typed failure outputs. Use when the user asks to "add a tool", "create a tool", "wrap an API as a tool", "build a `BaseTool`", "make a calculator/searc
6.1K stars
create-atomic-context-provider
Build a `BaseDynamicContextProvider` that injects a named, titled block into an agent's system prompt at every `run()` — current time, user identity, retrieved RAG docs, session state, cached DB schema. Use when the user asks to "add a context provider", "inject X into the prompt", "give the agent d
6.1K stars
framework
Guide for the Atomic Agents Python framework — schemas, agents, tools, context providers, prompts, orchestration, and provider configuration. Use when code imports from `atomic_agents`, defines an `AtomicAgent`, `BaseTool`, or `BaseIOSchema`, or the user asks about multi-agent orchestration or LLM-p
6.1K stars
Subagents
All subagents →explore
Read-only code explorer that the plugin's other agents dispatch to map a codebase — locate files, trace how a flow is wired, find every caller of a symbol, answer "where does X happen".
32.8K stars
scan-verifier
Restricted read-only verifier dispatched by the Claude Security scan workflow to vote on one candidate finding; not for direct invocation.
32.8K stars
scan-researcher
Restricted read-only vulnerability researcher dispatched by the Claude Security scan workflow; not for direct invocation or general exploration.
32.8K stars
MCP Servers
All mcp servers →Hooks
All hooks →PostToolUse (mcp__.*__find_columns|mcp__.*__get_dataset_columns|mcp__.*__get_dataset)
Pre-query column validation via schema caching. Catches unknown column errors before they hit the API by building a per-session schema cache from find_columns / get_dataset_columns / get_dataset results.
PreToolUse (mcp__.*__run_query)
Pre-query column validation via schema caching. Catches unknown column errors before they hit the API by building a per-session schema cache from find_columns / get_dataset_columns / get_dataset results.