In a Bit Cloud demonstration described by The New Stack, Model Context Protocol (MCP) let a fresh Claude Code session retrieve versioned component relationships, including a shared ticket entity used by an app and a service. The records gave the session a map to work from; the author then inspected source code and ran tests before changing the app.
The author disclosed working as an engineer at Bit Cloud, the platform used in the demonstration. That context matters: this was a first-hand account of one Bit Cloud setup, not a test of every MCP server.
What the fresh session found
The session began with an empty workspace, no local code, and no conversation history. The author said its only workspace guidance was the generic AGENTS.md created by bit new. Two MCP calls—read_scope followed by read_components—returned four components: a React app, an Express service backed by MongoDB, a shared ticket entity, and a gateway.
The app and service used the same version of the ticket entity. Across the four components, the records listed 16 pre-existing component dependencies, ten of them from Bit Design Sparks. For a new session, that versioned map supplied structural context that otherwise would have to be found in local files or recovered from prior conversation.
The author then imported the components and inspected their source. Claude Code made a client-side change to filter tickets by status and assignee in the app; it did not change the shared entity or the service. The account reports 41 passing tests, including nine new filtering tests.
What the test covered
The test result came with a specific qualification: MongoDB integration tests could be skipped if the CI runner could not start a temporary database. A passing test count therefore describes the reported run, while the database integration checks were not guaranteed to have run.
The app's API reference listed routes for a fake test service. The author did not check those routes against the real service. The author separately described manually creating a ticket, adding a comment, restarting the platform against the same database, and checking that both persisted.
The author described the setup as a demo using a predefined account and a public signing secret. Concurrency control, migrations, recovery procedures, and mandatory database tests were unfinished. Those details put the demonstration in its proper frame: MCP surfaced dependency information, while source inspection and testing remained part of the coding work.
Dependency records and persistent memory answer different questions. A versioned record captures which component version depends on another; memory or project notes can retain intent and decisions, such as why a feature was dropped. Anthropic likewise distinguishes MCP connections to external services and tools from Skills, which provide reusable knowledge or workflows (Claude Code feature overview). NeoTeo has also covered Claude Code's cross-project memory, a separate way to retain context.
Choose a scope for the MCP configuration
Anthropic describes three Claude Code MCP configuration scopes. Local scope applies to the current project on the developer's machine and is the default; project scope shares configuration with a team through .mcp.json in the project root; user scope applies to that developer's projects (Anthropic's MCP quickstart).
| Scope | Where it applies | Configuration sharing |
| Local | Current project on the developer's machine | Local to that machine |
| Project | The team project | Shared through .mcp.json at the project root |
| User | The developer's projects | User-level configuration across projects |
For a solo experiment, local scope keeps the configuration with the current machine and project. If teammates need the same project setup, project scope is the documented team-sharing option. User scope is for configuration carried across one developer's projects.
What MCP loads into context
Claude Code loads MCP tool names at session start and defers full tool schemas until they are needed. Anthropic describes idle MCP tools as having low context cost (feature overview). That is a statement about idle tools and schema loading—not a promise that calls or returned data use no context.
The practical distinction is simple: MCP connects Claude Code to an external system, and versioned component records can help a fresh session locate relationships in that system. In the Bit Cloud example, understanding and changing the app still involved inspecting code and running tests.
