Developers
Four ways in, from asking a question to shipping an integration. Every one runs against the same customer graph, with exactly the permissions of the person signed in - pick the door that matches how much code you want to write.
Which one am I?
Ordered by how much you build. Most people start at the top and only move down when they need to.
Add Noded as a connector to Claude, ChatGPT, Gemini or Microsoft Copilot and ask about your accounts, threads, meetings and records in plain language. Reads are permission-filtered to what you can already see; anything that would send or save comes back to you as a draft to approve.
The insights Noded watches on every account, the tables it brings in from your tools, the folders, the note templates and the agents that run on a schedule are all ordinary configuration. Set them up by talking to an AI assistant - it proposes a plan, you approve each piece - then adjust anything afterward in the Noded web client.
The @bigfootai/noded-sdk drops live customer context - people, accounts, activity, notes, memory - into a sidebar, a widget or an internal dashboard. One-line auth, typed helpers, no GraphQL to learn. Drop our AGENTS.md into your project and let Claude, Cursor or Lovable do the wiring.
Two references, one graph. The Graph API is the GraphQL API behind every Noded surface - read and write the graph from your own application, with every operation documented. The Provider SDK is the server SDK for feeding the graph from a system Noded doesn't connect to yet.
How the pieces fit
The MCP server, the SDK and the Graph API are the same API at three heights; providers are how data gets in. Whichever door you use, you see what the signed-in user can see, and nothing leaves Noded without their approval.
| Surface | Who it's for | What it does |
|---|---|---|
| MCP server | AI assistants - and the people and builders driving them | Search and read the graph, draft actions for review, configure the workspace conversationally. |
| @bigfootai/noded-sdk | Vibe coders and front-end developers | Typed helpers over the Graph API with sign-in handled. Escape hatch to raw GraphQL when you need it. |
| Graph API | Professional developers | Every query, mutation and subscription the Noded app itself uses. |
| Provider SDK | Developers and partners | Bring a new tool's data into the graph: auth, sync handlers, write-backs, functions and queries. |
Governance, ontology and model routing are handled underneath. Request developer access and we provision credentials for your app or provider.