From dataforce
Configure the Dataforce MCP server for whichever agents are installed locally — Claude Code (handled by the plugin manifest), Codex (~/.codex/config.toml), Cursor (~/.cursor/mcp.json). Prints copy-paste snippets for anything else. Verifies the OAuth bridge can reach https://dataforce.simplicitylabs.io/api/mcp. Use when a user installs the dataforce plugin, types /dataforce-setup, or asks to wire Dataforce into a new agent.
How this skill is triggered — by the user, by Claude, or both
Slash command
/dataforce:dataforce-setupThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill is bundled with the `dataforce` Claude Code plugin. It's the one-shot configurator that wires the Dataforce MCP server into every MCP-speaking agent the user has installed locally.
This skill is bundled with the dataforce Claude Code plugin. It's the one-shot configurator that wires the Dataforce MCP server into every MCP-speaking agent the user has installed locally.
~/.claude.json (Claude Code), ~/.codex/config.toml (Codex), ~/.cursor/mcp.json (Cursor). Note which exist.dataforce entry already exists, update in place. Never duplicate.npx -y mcp-remote https://dataforce.simplicitylabs.io/api/mcp --version 2>/dev/null (or equivalent dry-run) to confirm the package fetches and the URL is reachable.Already handled by the plugin's .mcp.json when the plugin is installed. This skill should NOT write to ~/.claude.json for Claude Code — that double-registers the server. Skip with a note: "Claude Code: handled by plugin manifest, no config write needed."
If the user has Claude Code installed but NOT via the plugin (rare — they ran the skill standalone), fall through and add to local scope:
claude mcp add dataforce -s user -- npx -y mcp-remote https://dataforce.simplicitylabs.io/api/mcp
Read ~/.codex/config.toml. If [mcp_servers.dataforce] block doesn't exist, append:
[mcp_servers.dataforce]
command = "npx"
args = ["-y", "mcp-remote", "https://dataforce.simplicitylabs.io/api/mcp"]
If it does exist, leave it (idempotent). Tell the user a backup at ~/.codex/config.toml.bak.<timestamp> was written before any change.
Read ~/.cursor/mcp.json (create if missing). Merge into top-level mcpServers:
{
"mcpServers": {
"dataforce": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://dataforce.simplicitylabs.io/api/mcp"]
}
}
}
Preserve existing entries. Backup file the same way.
Print both the JSON and the TOML forms, with a short note: "Drop the JSON into your agent's mcpServers config, or the TOML into the Codex-style equivalent. Both are equivalent — pick whichever your agent reads."
After writing configs, run:
npx -y mcp-remote --help >/dev/null 2>&1 && echo "mcp-remote available"
curl -sS -o /dev/null -w "%{http_code}\n" https://dataforce.simplicitylabs.io/api/mcp
mcp-remote should be on npx (lazy-installs on first use).If curl returns a network error, surface it: "Can't reach dataforce.simplicitylabs.io — check your network or VPN. The MCP server is hosted on Cloudflare Workers."
Print exactly:
Dataforce MCP configured for: <comma-separated agents>.
Next step:
1. Restart your agent (or open a new chat) so it picks up the new MCP server.
2. Ask it something dataforce-y, e.g. "what were yesterday's top SKUs?"
3. A browser tab will open the first time — log in via Clerk and click Allow.
4. Token sits in ~/.mcp-auth/ and refreshes automatically.
Tools available once authorized:
- get_orders
- get_stock_summary
- query_ads
- cross_channel_summary
Backups (if any config files were modified):
- <list of .bak.<ts> paths>
If invoked with --remove or the user asks to uninstall:
/plugin uninstall dataforce (don't try to remove the MCP manually from a plugin-managed entry).dataforce block from the relevant config, leave everything else alone, write a .bak.<ts> first.~/.mcp-auth/ and is managed by mcp-remote itself. This skill only writes the command that invokes mcp-remote.dfp_*) still works for power users, but it's not the default install path. If the user has a PAT and wants to use it instead of OAuth, point them at the dashboard at https://dataforce.simplicitylabs.io/settings/tokens — don't try to manage PATs from this skill.npx claudepluginhub simplicity-labs/dataforce-plugin --plugin dataforceProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.