@arcbridge/mcp-server 0.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +21 -0
- package/README.md +101 -0
- package/dist/index.d.ts +2 -0
- package/dist/index.js +3750 -0
- package/dist/index.js.map +1 -0
- package/package.json +47 -0
package/LICENSE
ADDED
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
MIT License
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2026 Achim Kuehn
|
|
4
|
+
|
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
+
in the Software without restriction, including without limitation the rights
|
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
+
furnished to do so, subject to the following conditions:
|
|
11
|
+
|
|
12
|
+
The above copyright notice and this permission notice shall be included in all
|
|
13
|
+
copies or substantial portions of the Software.
|
|
14
|
+
|
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
21
|
+
SOFTWARE.
|
package/README.md
ADDED
|
@@ -0,0 +1,101 @@
|
|
|
1
|
+
# @arcbridge/mcp-server
|
|
2
|
+
|
|
3
|
+
MCP server for ArcBridge — exposes 26 architecture tools to AI coding agents via the [Model Context Protocol](https://modelcontextprotocol.io).
|
|
4
|
+
|
|
5
|
+
## Install
|
|
6
|
+
|
|
7
|
+
```bash
|
|
8
|
+
npm install -g @arcbridge/mcp-server
|
|
9
|
+
```
|
|
10
|
+
|
|
11
|
+
## Setup
|
|
12
|
+
|
|
13
|
+
Add to your project's `.mcp.json`:
|
|
14
|
+
|
|
15
|
+
```json
|
|
16
|
+
{
|
|
17
|
+
"mcpServers": {
|
|
18
|
+
"arcbridge": {
|
|
19
|
+
"command": "npx",
|
|
20
|
+
"args": ["@arcbridge/mcp-server"]
|
|
21
|
+
}
|
|
22
|
+
}
|
|
23
|
+
}
|
|
24
|
+
```
|
|
25
|
+
|
|
26
|
+
Restart your AI agent (Claude Code, etc.) and approve the MCP server when prompted.
|
|
27
|
+
|
|
28
|
+
## Tools
|
|
29
|
+
|
|
30
|
+
### Lifecycle
|
|
31
|
+
|
|
32
|
+
| Tool | Description |
|
|
33
|
+
|------|-------------|
|
|
34
|
+
| `arcbridge_init_project` | Initialize ArcBridge in a project directory |
|
|
35
|
+
| `arcbridge_get_project_status` | Current phase, task completion, quality summary |
|
|
36
|
+
|
|
37
|
+
### Architecture
|
|
38
|
+
|
|
39
|
+
| Tool | Description |
|
|
40
|
+
|------|-------------|
|
|
41
|
+
| `arcbridge_get_building_blocks` | All blocks with code paths and quality links |
|
|
42
|
+
| `arcbridge_get_building_block` | Deep dive: one block with ADRs, tasks, scenarios |
|
|
43
|
+
| `arcbridge_get_quality_scenarios` | Quality requirements, filterable by category/status |
|
|
44
|
+
| `arcbridge_get_relevant_adrs` | ADRs for a file path or building block |
|
|
45
|
+
|
|
46
|
+
### Planning
|
|
47
|
+
|
|
48
|
+
| Tool | Description |
|
|
49
|
+
|------|-------------|
|
|
50
|
+
| `arcbridge_get_phase_plan` | All phases with tasks and acceptance criteria |
|
|
51
|
+
| `arcbridge_get_current_tasks` | Tasks for the active phase |
|
|
52
|
+
| `arcbridge_update_task` | Mark tasks in-progress, done, or blocked |
|
|
53
|
+
| `arcbridge_create_task` | Add a task to any phase |
|
|
54
|
+
|
|
55
|
+
### Code Intelligence
|
|
56
|
+
|
|
57
|
+
| Tool | Description |
|
|
58
|
+
|------|-------------|
|
|
59
|
+
| `arcbridge_reindex` | Index/re-index TypeScript symbols (incremental) |
|
|
60
|
+
| `arcbridge_search_symbols` | Search by name, kind, file path, or building block |
|
|
61
|
+
| `arcbridge_get_symbol` | Full detail: signature, source, relationships |
|
|
62
|
+
| `arcbridge_get_dependency_graph` | Import/dependency graph for a module |
|
|
63
|
+
|
|
64
|
+
### React & Next.js
|
|
65
|
+
|
|
66
|
+
| Tool | Description |
|
|
67
|
+
|------|-------------|
|
|
68
|
+
| `arcbridge_get_component_graph` | Component hierarchy with props, state, context flow |
|
|
69
|
+
| `arcbridge_get_route_map` | Next.js App Router routes with layouts and middleware |
|
|
70
|
+
| `arcbridge_get_boundary_analysis` | Server/client boundary analysis |
|
|
71
|
+
|
|
72
|
+
### Architecture Bridge
|
|
73
|
+
|
|
74
|
+
| Tool | Description |
|
|
75
|
+
|------|-------------|
|
|
76
|
+
| `arcbridge_check_drift` | Detect drift between docs and code |
|
|
77
|
+
| `arcbridge_get_guidance` | Context-aware guidance for a file or block |
|
|
78
|
+
| `arcbridge_get_open_questions` | Unresolved architectural questions and risks |
|
|
79
|
+
| `arcbridge_propose_arc42_update` | Generate arc42 update proposals from code changes |
|
|
80
|
+
| `arcbridge_get_practice_review` | 5-dimension review: architecture, security, testing, docs, complexity |
|
|
81
|
+
|
|
82
|
+
### Roles & Sync
|
|
83
|
+
|
|
84
|
+
| Tool | Description |
|
|
85
|
+
|------|-------------|
|
|
86
|
+
| `arcbridge_complete_phase` | Validate phase gates and transition to next phase |
|
|
87
|
+
| `arcbridge_activate_role` | Load agent role with tools and pre-loaded context |
|
|
88
|
+
| `arcbridge_verify_scenarios` | Run linked tests for quality scenarios |
|
|
89
|
+
| `arcbridge_run_role_check` | Run a role's quality checks against code |
|
|
90
|
+
|
|
91
|
+
## How It Works
|
|
92
|
+
|
|
93
|
+
The server communicates over stdio using the MCP protocol. Each tool call receives a `target_dir` parameter pointing to an ArcBridge-initialized project. The server manages a SQLite database (`.arcbridge/index.db`) that caches architecture docs, indexed symbols, and planning state.
|
|
94
|
+
|
|
95
|
+
Data flow: **YAML/markdown (source of truth) -> SQLite (query cache) -> MCP tools (agent interface)**
|
|
96
|
+
|
|
97
|
+
All mutations (task updates, phase transitions, scenario results) write back to both the database and the source YAML files, so the docs stay in sync.
|
|
98
|
+
|
|
99
|
+
## License
|
|
100
|
+
|
|
101
|
+
[MIT](../../LICENSE)
|
package/dist/index.d.ts
ADDED