You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A monorepo containing multiple Model Context Protocol (MCP) servers for Truvera API integrations.
5
+
A monorepo containing Model Context Protocol (MCP) servers for Truvera API integrations. MCP servers let AI assistants (Claude, GitHub Copilot, etc.) call real Truvera API operations as tools.
The main MCP server that exposes Truvera API functionality as MCP tools. Supports verifiable credentials, DIDs, presentations, and more.
50
+
The server is now running and ready to connect to your AI assistant. See [Connecting to AI Assistants](#connecting-to-ai-assistants) below.
33
51
34
-
**📖 [Read the full documentation](apps/truvera-api/README.md)**
52
+
### Alternative: Run locally without Docker
35
53
36
-
**Quick start:**
37
54
```bash
38
55
cd apps/truvera-api
39
-
npm install
40
-
npm run dev
56
+
MCP_MODE=http npm run dev # HTTP transport (recommended)
41
57
```
42
58
43
-
## Docker Compose
59
+
> **Transport modes:** HTTP transport is well-tested and recommended for development and production. STDIO transport is experimental — use it only if your client requires it and you are comfortable with limited test coverage.
44
60
45
-
You can run all MCP servers using Docker Compose from the root directory:
61
+
## Connecting to AI Assistants
46
62
47
-
```bash
48
-
# Start all services
49
-
docker-compose up -d
63
+
Once the server is running in HTTP mode on port 3000:
The workspace `.vscode/mcp.json` is already configured. Start the server, then in the Copilot chat pane click **Configure tools...** → **Update tools** under `truvera-mcp-service-vs-code`.
61
86
62
-
1. Create a new directory under `apps/`:
63
-
```bash
64
-
mkdir -p apps/your-new-server
65
-
```
87
+
## MCP Inspector (Shared for All Servers)
66
88
67
-
2. Set up your server structure with:
68
-
-`package.json` - Dependencies and scripts
69
-
-`tsconfig.json` - TypeScript configuration
70
-
-`src/` - Source code
71
-
-`tests/` - Test suites
72
-
-`README.md` - Documentation
89
+
Use MCP Inspector to debug or manually exercise tools from any MCP server in this repo (for example, `apps/truvera-api` now, and `apps/wallet-server` as it matures).
73
90
74
-
3. Add build tasks to `.vscode/tasks.json`
91
+
### 1. Start the Inspector UI
75
92
76
-
4. Add CI/CD steps to `.github/workflows/ci.yml`
93
+
```bash
94
+
npx @modelcontextprotocol/inspector
95
+
```
77
96
78
-
5. Add service to `docker-compose.yml` if needed
97
+
### 2. Start the MCP server you want to inspect
79
98
80
-
### VS Code Configuration
99
+
Truvera API server (HTTP mode):
81
100
82
-
The workspace is configured with tasks for each MCP server:
83
-
-`build:truvera` - Build the Truvera server
84
-
-`dev:truvera` - Run Truvera server in development mode
101
+
```bash
102
+
npm run docker:run:api
103
+
# or: cd apps/truvera-api && MCP_MODE=http npm run dev
104
+
```
85
105
86
-
Use `Ctrl+Shift+B` (or `Cmd+Shift+B` on macOS) to access build tasks.
106
+
Wallet server (HTTP mode, work in progress):
87
107
88
-
## Environment Variables
108
+
```bash
109
+
cd apps/wallet-server
110
+
MCP_MODE=http npm run dev
111
+
```
89
112
90
-
Each MCP server may require different environment variables. See the individual server README files for details.
113
+
### 3. Connect from Inspector
91
114
92
-
For the Truvera server, see [apps/truvera-api/README.md](apps/truvera-api/README.md#environment-variables).
If connection fails, check the target server health endpoint first (`/health`) and confirm ports/env values.
95
122
96
-
This repository uses GitHub Actions for continuous integration. The workflow:
97
-
- Builds each MCP server
98
-
- Runs unit, integration, and e2e tests
99
-
- Performs smoke tests
123
+
## Repository Structure
100
124
101
-
See [.github/workflows/ci.yml](.github/workflows/ci.yml) for details.
125
+
```
126
+
truvera-mcp-server/
127
+
├── apps/
128
+
│ ├── truvera-api/ # ✅ Truvera REST API MCP server (production-ready)
129
+
│ └── wallet-server/ # 🚧 Wallet SDK MCP server (work in progress)
130
+
├── packages/
131
+
│ └── mcp-shared/ # Shared MCP server bootstrap utilities
132
+
├── .vscode/ # VS Code tasks, launch configs, MCP server config
133
+
├── docker-compose.yml # Compose file for running the truvera-api service
134
+
└── README.md # This file
135
+
```
102
136
103
-
## License
137
+
## Development Commands
104
138
105
-
See individual MCP server directories for licensing information.
139
+
Run from the repo root:
140
+
141
+
```bash
142
+
npm install # Install all workspace dependencies
143
+
npm run build # Build all packages and apps
144
+
npm run test# Run all tests
145
+
npm run docker:build:api # Build the truvera-api Docker image
146
+
npm run docker:run:api # Run the truvera-api container on port 3000
147
+
```
148
+
149
+
For development server with hot-reload (HTTP transport):
150
+
151
+
```bash
152
+
MCP_MODE=http npm run dev:api
153
+
```
154
+
155
+
See [apps/truvera-api/README.md](apps/truvera-api/README.md) for full documentation including all environment variables, available tools, and testing instructions.
156
+
157
+
## CI/CD
158
+
159
+
GitHub Actions builds all apps, runs unit and integration tests, and performs a smoke test on every push. See [.github/workflows/ci.yml](.github/workflows/ci.yml) for details.
106
160
107
161
## Contributing
108
162
@@ -111,5 +165,3 @@ See individual MCP server directories for licensing information.
111
165
3. Ensure tests pass: `npm test`
112
166
4. Submit a pull request
113
167
114
-
For server-specific contribution guidelines, see the README in each app directory.
0 commit comments