@spec-r/mcp-server 0.3.0 → 0.3.1
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/README.md +10 -9
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
|
1
1
|
# @spec-r/mcp-server
|
|
2
2
|
|
|
3
|
-
MCP server
|
|
3
|
+
MCP server — give Claude Code and other AI agents direct access to your specifications.
|
|
4
4
|
|
|
5
5
|
## Setup
|
|
6
6
|
|
|
7
7
|
**1. Get your API key**
|
|
8
8
|
|
|
9
|
-
Go to
|
|
9
|
+
Go to Settings → API Keys → Create.
|
|
10
10
|
|
|
11
11
|
**2. Add to your MCP config**
|
|
12
12
|
|
|
@@ -45,9 +45,9 @@ Global (`~/.claude/settings.json` or Claude Desktop config) — omit `SPECR_PROJ
|
|
|
45
45
|
|
|
46
46
|
## Environment variables
|
|
47
47
|
|
|
48
|
-
| Variable | Required | Description
|
|
49
|
-
| ------------------ | -------- |
|
|
50
|
-
| `SPECR_API_KEY` | Yes | API key from Settings → API Keys
|
|
48
|
+
| Variable | Required | Description |
|
|
49
|
+
| ------------------ | -------- | ----------------------------------------------------- |
|
|
50
|
+
| `SPECR_API_KEY` | Yes | API key from Settings → API Keys |
|
|
51
51
|
| `SPECR_BASE_URL` | No | Override API base URL (default: `https://spec-r.app`) |
|
|
52
52
|
| `SPECR_PROJECT_ID` | No | Default project UUID — skip to let the agent discover it |
|
|
53
53
|
|
|
@@ -98,10 +98,10 @@ Shared resources are reusable entities (`data_model`, `persona`, `enum_definitio
|
|
|
98
98
|
|
|
99
99
|
### AI analysis
|
|
100
100
|
|
|
101
|
-
| Tool
|
|
102
|
-
|
|
|
103
|
-
| `analyze_screenshot
|
|
104
|
-
| `analyze_feedback`
|
|
101
|
+
| Tool | Description |
|
|
102
|
+
| -------------------- | --------------------------------------------------------------- |
|
|
103
|
+
| `analyze_screenshot` | Analyze a wireframe/mockup and extract structured specs |
|
|
104
|
+
| `analyze_feedback` | Analyze client feedback and extract prioritized feature requests |
|
|
105
105
|
|
|
106
106
|
## Resources
|
|
107
107
|
|
|
@@ -118,6 +118,7 @@ Before calling `publish_spec` or `add_block`, read `spec-r://block-types` to get
|
|
|
118
118
|
|
|
119
119
|
## Tips
|
|
120
120
|
|
|
121
|
+
- No project yet? Use `create_project` to set one up — the agent will return a project ID to use in subsequent calls
|
|
121
122
|
- Omit `SPECR_PROJECT_ID` in global configs — the agent uses `list_projects` to discover IDs
|
|
122
123
|
- Use `get_spec` with `format: "agent"` for the most implementation-ready output
|
|
123
124
|
- Define cross-cutting entities (User, enums, external APIs) as shared resources with `create_resource` — avoids repeating the same data model in every spec
|