codeport 0.0.0-stage → 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.
Files changed (3) hide show
  1. package/README.md +63 -2
  2. package/index.js +2579 -0
  3. package/package.json +33 -4
package/README.md CHANGED
@@ -1,3 +1,64 @@
1
- # Temporary Holding Version
1
+ # Codeport MCP server
2
2
 
3
- This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
3
+ Lets Claude Code, Codex and other MCP clients sign in to Codeport and analyze the project you
4
+ have open: detect its stack, estimate monthly hosting cost on nine platforms and recommend where
5
+ to host it.
6
+
7
+ **Your code stays on your machine.** Analysis runs locally; only the stack profile (frameworks,
8
+ services, the _names_ of required settings) is sent to Codeport. Secret values are never read
9
+ into it, and your session token is kept in the OS keychain and never shown to the AI.
10
+
11
+ ## Tools
12
+
13
+ | Tool | What it does |
14
+ | --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
15
+ | `auth_start`, `auth_verify` | Sign in or create an account with a 6-digit code sent to your work email |
16
+ | `whoami`, `sign_out` | Current account; sign out on this machine |
17
+ | `analyze_project` | Detect the stack, save the project in your organization's catalog, first estimate |
18
+ | `estimate_cost` | Monthly cost on every platform for a load (Team / Department / Company or your numbers); `platform` gives an itemized bill with sources |
19
+ | `recommend_target` | Ranking by simplicity, cost and fit, with reasons; names the best platform Codeport can deploy to |
20
+
21
+ ## Set up
22
+
23
+ Needs Node.js 22 or newer. Nothing to clone or build: `npx` downloads the server on first use.
24
+
25
+ Claude Code (all projects):
26
+
27
+ ```sh
28
+ claude mcp add codeport --scope user -- npx -y codeport
29
+ ```
30
+
31
+ Codex (`~/.codex/config.toml`):
32
+
33
+ ```toml
34
+ [mcp_servers.codeport]
35
+ command = "npx"
36
+ args = ["-y", "codeport"]
37
+ ```
38
+
39
+ Claude Desktop (`claude_desktop_config.json`):
40
+
41
+ ```json
42
+ { "mcpServers": { "codeport": { "command": "npx", "args": ["-y", "codeport"] } } }
43
+ ```
44
+
45
+ For the staging environment add `CODEPORT_API_URL`, e.g.
46
+ `claude mcp add codeport --scope user --env CODEPORT_API_URL=https://<staging-api-host> -- npx -y codeport`.
47
+
48
+ ### From a clone (development)
49
+
50
+ ```sh
51
+ corepack enable && pnpm install && pnpm --filter @codeport/mcp... build
52
+ claude mcp add codeport -- node /path/to/codeport/apps/mcp/dist/index.js
53
+ ```
54
+
55
+ ### Releasing
56
+
57
+ `pnpm --filter @codeport/mcp pack:npm` bundles the server into `apps/mcp/npm/` (the
58
+ `@codeport/*` workspace packages are inlined; only the MCP SDK, zod and the OS keychain binding
59
+ stay as dependencies). Bump `version` in `package.json` and `src/version.ts`, merge, then push a
60
+ tag `mcp-v<version>`: the "Release codeport to npm" workflow tests, packs and publishes it
61
+ with npm trusted publishing.
62
+
63
+ Then, in a project folder, ask: _"Sign in to Codeport with me@company.com"_, paste the code, and
64
+ _"Analyze this project with Codeport and tell me where to host it."_