connect-atlas-mcp
Skill6 starsChanged 11 days agoApache-2.0View on GitHub
MUST be used when a Fusion Custom apps Start building or Build app prompt is in chat and Industrial / Atlas MCP must be connected. Triggers: ---Start Building---, Intent sketch from Fusion Custom apps, createdVia fusion.customApps.buildPrompt, "Industrial MCP for this project", or a Fusion MCP command such as claude mcp add-json cognite, cursor --add-mcp, or code --add-mcp. Do not use for docs MCP or dm-graph-traversal.
In this repository34 other files it gives its agents.
- aura-reviewSkill
- call-cognite-functionSkill
- code-qualitySkill
- correctness-and-error-handlingSkill
- create-agentSkill
- create-client-toolSkill
- dependencies-auditSkill
- designSkill
- dm-graph-traversalSkill
- dm-limits-and-best-practicesSkill
- flows-app-briefSkill
- flows-code-reviewSkill
- flows-design-reviewSkill
- flows-external-app-submitSkill
- flows-review-checksSkill
- graph-viewerSkill
- handle-startup-stateSkill
- hide-show-shellSkill
- integrate-atlas-chatSkill
- integrate-file-viewerSkill
- integrate-fusion-agentSkill
- integrate-todo-listSkill
- migrate-app-to-flowsSkill
- performanceSkill
- pull-changes-resolve-conflictsSkill
- reveal-3dSkill
- securitySkill
- setup-flows-authSkill
- setup-python-toolsSkill
- skill-creatorSkill
- start-flows-appSkill
- test-coverageSkill
- tygenSkill
- use-topbarSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 33
If the prompt carries a command for another tool, treat it the same way.
- Very specific: line 37
If ---Start Building--- is missing, or the MCP URL or command is missing, the prompt was truncated.
- Very specific: line 41
Do not paste tokens. Do not scrape the CLI keychain.
- Distinctive: line 47
Run the command verbatim in a terminal.
- Very specific: line 66
Prefer MCP list/query. Name models relevant to the Fusion intent.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Connect Atlas MCP (Fusion launch)
The Fusion prompt has a block like this, with one command for the tool Fusion opened:
Industrial MCP for this project:
- MCP URL: https://<cluster>/api/v1/projects/<project>/ai/mcp
- Run this command as written, then finish the OAuth flow in the browser:
<command>Known command shapes:
| Tool | Command starts with |
| Claude | claude mcp add-json cognite '{...}' |
| Cursor | cursor --add-mcp '{...}' |
| Copilot / VS Code | code --add-mcp '{...}' |
If the prompt carries a command for another tool, treat it the same way. Do
not rebuild the URL from cluster or project. Do not invent client ids,
callback ports, or switch add-json to claude mcp add.
If ---Start Building--- is missing, or the MCP URL or command is missing,
the prompt was truncated. Ask the builder to Copy from Fusion and paste, then
continue.
Do not paste tokens. Do not scrape the CLI keychain. The prompt's npx
@cognite/cli@latest auth login signs in the CLI; it is not the MCP
credential.
1. Run Fusion's command as written
Run the command verbatim in a terminal. This is the happy path.
On Windows the single-quoted JSON is POSIX shell quoting. PowerShell 7.3+
accepts it as-is. In Windows PowerShell 5.1 or cmd.exe, wrap the JSON in
double quotes and escape inner quotes as \". Change only the quoting, never
the JSON.
Fallback, only if the command cannot run (CLI not on PATH, tool refuses the
flag): add the same server by hand to the tool's MCP config. Use the JSON from
the command, name the server cognite, and keep cognite-docs if the
template has it.
2. Finish OAuth in the browser
Enable the cognite server and complete the browser flow. Success is
connected in the tool, not a file on disk.
3. Explore this project's data models
Prefer MCP list/query. Name models relevant to the Fusion intent. Do not
invent spaces or views. Graph reads in app code: dm-graph-traversal.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.