capix-mcp 2.1.0

package/CONTRIBUTING.md

@@ -0,0 +1,168 @@
+# Contributing to Capix MCP
+
+Thank you for your interest in contributing to Capix MCP! This guide covers how to build, test, and contribute to the project.
+
+## Prerequisites
+
+- **Node.js** >= 18
+- **TypeScript** 5.7+ (installed as a dev dependency)
+- A Capix account (sign up at [capix.network](https://capix.network)) for integration testing
+
+## Getting started
+
+```bash
+# Clone the repository
+git clone https://github.com/CapIX-Protocol/CapIX-MCP.git
+cd CapIX-MCP
+
+# Install dependencies
+npm install
+
+# Build the project
+npm run build
+
+# Run the server locally
+npm start
+
+# Or run in development mode (auto-restart on file changes)
+npm run dev
+```
+
+## Project structure
+
+```
+capix-mcp/
+├── bin/
+│   └── capix-mcp.js          # CLI entry point (imports dist/index.js)
+├── src/
+│   ├── index.ts              # CLI argument parsing + command dispatch
+│   ├── server.ts             # McpServer assembly + transport wiring
+│   ├── client.ts             # Capix API client + auth providers
+│   ├── tools.ts              # All 59 tool definitions (Zod schemas + handlers)
+│   ├── types.ts              # Shared types (branded IDs, money, errors)
+│   ├── resources.ts          # MCP resources (capix:// URIs)
+│   └── prompts.ts            # MCP guided prompts
+├── package.json
+├── tsconfig.json
+└── README.md
+```
+
+## Development
+
+### Build
+
+```bash
+npm run build          # Compile TypeScript to dist/
+```
+
+### Type-check
+
+```bash
+npm run typecheck      # tsc --noEmit (no output = success)
+```
+
+### Local testing
+
+```bash
+# Authenticate
+npm start -- login
+
+# Run the doctor to verify auth + tool inventory
+npm start -- doctor
+
+# Start the server on stdio
+npm start
+
+# Start with HTTP transport
+npm start -- server --http 8080 --token my-secret
+```
+
+### Diagnosing issues
+
+```bash
+npm start -- doctor     # Auth status, base URL, tool inventory
+npm start -- --health   # JSON health report
+```
+
+## Code style
+
+### TypeScript conventions
+
+- **Strict mode** is enabled (`"strict": true` in tsconfig.json). All code must pass type-checking.
+- **ESM modules**: the project uses `"type": "module"` in package.json. Use `.js` extensions in imports (e.g., `import { X } from "./foo.js"`).
+- **No `any`**: prefer `unknown` + type narrowing over `any`. Use Zod schemas for runtime validation of external input.
+- **Branded types**: IDs (`DeploymentId`, `QuoteId`, etc.) are branded string types. Never construct them with raw string casts — use the factory functions or Zod schemas.
+
+### Tool definitions
+
+Every tool is defined with `defineTool()`:
+
+```typescript
+defineTool({
+  name: "capix_example",
+  description: "Short description. Read-only | Billable; requires approval.",
+  scope: "discovery",
+  ...READ_ONLY,           // or BILLABLE, APPROVAL_ONLY
+  inputShape: {
+    // Zod raw shape — validated by the MCP SDK before dispatch
+  },
+  outputShape: {
+    // Optional Zod raw shape for structured output validation
+  },
+  handler: async (args, { client, ctx }) => {
+    // Thin: translate Zod-validated args → client call → return upstream JSON
+    return client.get("/api/v1/example", { id: args.id });
+  },
+})
+```
+
+Key rules for tool handlers:
+
+1. **Handlers are thin** — they translate arguments into client calls and return the upstream JSON. No business logic in the handler.
+2. **Billable tools** must use `callBillable()` which enforces the `approvalToken` gate.
+3. **Read-only tools** use `...READ_ONLY` and auto-run after authentication.
+4. **Errors** — let `CapixApiError` propagate. The server wrapper catches it and surfaces it as a structured MCP error.
+
+### Commits
+
+- Use clear, descriptive commit messages.
+- Reference issues in the format `Fixes #123` or `Closes #456`.
+
+## Adding a new tool
+
+1. Add the tool definition in `src/tools.ts` using `defineTool()`.
+2. Place it in the appropriate scope array (`discoveryTools`, `lifecycleTools`, etc.).
+3. Update the tool count comment at the top of `tools.ts`.
+4. Update the README tool table.
+5. Run `npm run typecheck` to verify.
+6. Run `npm start -- doctor` to verify the new tool appears in the inventory.
+
+## Pull request process
+
+1. **Fork** the repository and create your branch from `main`.
+2. **Write tests** if applicable (the project currently relies on integration testing via `doctor` and manual verification).
+3. **Type-check**: `npm run typecheck` must pass with zero errors.
+4. **Build**: `npm run build` must succeed.
+5. **Document**: update the README tool table if you added/changed a tool.
+6. **Submit** a pull request with a clear description of what changed and why.
+
+### PR checklist
+
+- [ ] `npm run typecheck` passes
+- [ ] `npm run build` succeeds
+- [ ] New tools are documented in README.md
+- [ ] Tool count in `tools.ts` header comment is updated
+- [ ] No secrets or API keys committed
+
+## Reporting issues
+
+- **Bugs**: open a [GitHub issue](https://github.com/CapIX-Protocol/CapIX-MCP/issues) with:
+  - `capix-mcp --version` output
+  - `capix-mcp doctor` output (redact any sensitive info)
+  - Steps to reproduce
+  - Expected vs actual behavior
+- **Security issues**: do NOT open a public issue. Email security@capix.network.
+
+## License
+
+By contributing, you agree that your contributions will be licensed under the [Apache-2.0 License](LICENSE).

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Capix Network
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,309 @@
+# Capix MCP — infrastructure controls for AI agents
+
+Capix MCP is a [Model Context Protocol](https://modelcontextprotocol.io) server that gives AI coding agents the ability to deploy and manage private LLM instances, GPU compute, websites, and verified workloads on the [Capix network](https://capix.network) — all through a single authenticated connection.
+
+<!--PEnd of auto-generated overview -->
+
+## Quick start
+
+```bash
+npm install -g @capix/mcp
+capix-mcp login
+```
+
+That's it. Your AI agent can now deploy models, manage compute, and build websites on Capix.
+
+## How it works
+
+Capix MCP exposes **59 tools** grouped into seven scopes. The server speaks stdio (for local agent integration) and streamable HTTP (for remote/hosted use). Authentication is handled via OAuth PKCE (through the `@capix/auth-broker`) or a simple `CAPIX_API_KEY` environment variable.
+
+Read-only tools auto-run after authentication. Billable tools require a bound `approvalToken` — the agent obtains this after quoting the cost upstream, so no spend happens without explicit user consent.
+
+## Install
+
+### Global (recommended)
+
+```bash
+npm install -g @capix/mcp
+```
+
+### From source
+
+```bash
+git clone https://github.com/CapIX-Protocol/CapIX-MCP.git
+cd CapIX-MCP
+npm install
+npm run build
+```
+
+## Authentication
+
+Run the login command for an interactive OAuth flow:
+
+```bash
+capix-mcp login
+```
+
+Or set environment variables directly:
+
+| Variable | Description | Default |
+|---|---|---|
+| `CAPIX_BASE_URL` | Capix network URL | `https://capix.network` |
+| `CAPIX_API_KEY` | Session token or API key (fallback when no OAuth) | — |
+| `CAPIX_REFRESH_TOKEN` | OAuth refresh token (auto-discovery: IDE/CLI sets this) | — |
+| `CAPIX_PROJECT_ID` | Default project id for unscoped reads | — |
+| `CAPIX_OAUTH_CLIENT_ID` | OAuth client id | `capix-mcp` |
+| `CAPIX_MCP_HTTP_PORT` | Port for the streamable HTTP transport | — |
+| `CAPIX_MCP_HTTP_TOKEN` | Bearer service token guarding the HTTP transport | — |
+
+### Auto-discovery
+
+When run as `capix-mcp server --stdio`, the server resolves credentials in this order:
+
+1. **`CAPIX_API_KEY`** in env — session token set by the IDE or CLI
+2. **`CAPIX_REFRESH_TOKEN`** in env — the broker refreshes to obtain an access token
+3. **Stored broker credentials** — OS keyring or `~/.capix/credentials.json`
+
+If none are found, the server starts but tool calls will fail with `not_authenticated` until credentials are resolved. CapixIDE and Capix Code set `CAPIX_REFRESH_TOKEN` automatically when signed in.
+
+### Health check
+
+```bash
+capix-mcp --health
+```
+
+Outputs a JSON status report: version, auth method, tool count, and per-scope breakdown.
+
+## Wire into your AI agent
+
+### CapixIDE / Capix Code
+
+The MCP server **auto-discovers** in both CapixIDE and Capix Code when you're signed in. The IDE sets `CAPIX_REFRESH_TOKEN` in the environment before spawning the server, so no manual configuration is needed.
+
+To verify:
+
+```bash
+capix-mcp doctor
+```
+
+### opencode
+
+Add to `~/.config/capix-code/opencode.json`:
+
+```jsonc
+{
+  "mcp": {
+    "capix": {
+      "type": "local",
+      "command": ["capix-mcp"],
+      "enabled": true
+    }
+  }
+}
+```
+
+### Claude Code
+
+Add to `.mcp.json` in your project root:
+
+```json
+{
+  "mcpServers": {
+    "capix": {
+      "command": "capix-mcp"
+    }
+  }
+}
+```
+
+### Other MCP-compatible agents
+
+Any agent that supports the Model Context Protocol can connect. Start the server on stdio (the default):
+
+```bash
+capix-mcp
+```
+
+Or with streamable HTTP:
+
+```bash
+capix-mcp server --http 8080 --token <service-token>
+```
+
+## Tools (59)
+
+All tools are prefixed with `capix_`. Read-only tools auto-run after authentication. Billable tools require a bound `approvalToken`.
+
+### Discovery (9) — read-only
+
+| Tool | Description |
+|---|---|
+| `capix_account` | Inspect the authenticated account: wallet, balance, limits, active deployments/agents |
+| `capix_balance` | Get the cash balance (available / held / total) for the account |
+| `capix_projects` | List projects visible to the authenticated account |
+| `capix_compute_catalog` | List the live compute capability catalog (provider / region / tier / price) |
+| `capix_model_catalog` | List the live model endpoint catalog (model id, context length, price) |
+| `capix_network_status` | Inspect network and gateway status (provider health, lanes, emergency flags) |
+| `capix_deployments` | List deployments with phase + allocation state |
+| `capix_receipts` | List work receipts for the account |
+| `capix_attestations` | List attestation records for the account |
+
+### Planning (6) — read-only
+
+| Tool | Description |
+|---|---|
+| `capix_compute_plan` | Plan a compute deployment (matching models to offers) |
+| `capix_compute_quote` | Get a canonical quote for a compute deployment |
+| `capix_model_plan` | Plan a model endpoint deployment |
+| `capix_model_quote` | Get a canonical quote for a model endpoint plan |
+| `capix_stack_validate` | Validate a multi-component stack definition |
+| `capix_stack_plan` | Plan a multi-component stack deployment |
+
+### Lifecycle (7) — billable, requires approval
+
+| Tool | Description |
+|---|---|
+| `capix_deploy` | Deploy a resource (compute or model endpoint) from a quote |
+| `capix_start` | Start a stopped deployment |
+| `capix_stop` | Stop a running deployment |
+| `capix_restart` | Restart a deployment (stop + start cycle) |
+| `capix_delete` | Delete a deployment permanently |
+| `capix_extend` | Extend a deployment's lifetime |
+| `capix_cancel` | Cancel an in-progress operation |
+
+### Networking (8) — billable, requires approval
+
+| Tool | Description |
+|---|---|
+| `capix_create_vpc` | Create a VPC for a project |
+| `capix_create_endpoint` | Create a network endpoint for a deployment |
+| `capix_expose_port` | Expose a port on a deployment |
+| `capix_close_port` | Close a previously exposed port |
+| `capix_inspect_routes` | Inspect the routing table for a deployment |
+| `capix_create_private_connection` | Create a private connection between deployments |
+| `capix_request_dedicated_ip` | Request a dedicated IP for a deployment |
+| `capix_port_forward` | Set up port forwarding for a deployment |
+
+### Testing (6) — mixed
+
+| Tool | Description |
+|---|---|
+| `capix_create_test_env` | Create an isolated test environment |
+| `capix_run_health_checks` | Run health checks against a deployment |
+| `capix_run_bounded_command` | Run a bounded shell command inside a deployment |
+| `capix_inspect_logs` | Inspect deployment logs |
+| `capix_inspect_metrics` | Inspect deployment metrics |
+| `capix_destroy_task_resources` | Destroy resources created by a specific task |
+
+### Verification (6) — read-only
+
+| Tool | Description |
+|---|---|
+| `capix_fetch_attestation` | Fetch an attestation record |
+| `capix_verify_attestation` | Verify an attestation against its expected measurements |
+| `capix_fetch_proof` | Fetch a zkVM proof artifact for a workload |
+| `capix_verify_proof` | Verify a zkVM proof artifact against its public inputs |
+| `capix_inspect_measurement` | Inspect the measurement of a workload |
+| `capix_inspect_receipt` | Inspect a work receipt in detail |
+
+### Website (17)
+
+| Tool | Description |
+|---|---|
+| `capix_website_project_string_check` | Check a website project string for validity |
+| `capix_website_create` | Create a new website project |
+| `capix_website_detect` | Auto-detect website framework from a repository |
+| `capix_website_plan` | Plan a website deployment (build + hosting plan) |
+| `capix_website_quote` | Get a canonical quote for a website deploy |
+| `capix_website_deploy` | Deploy a website (build + host) |
+| `capix_website_preview` | Create a preview deployment |
+| `capix_website_promote` | Promote a preview to production |
+| `capix_website_rollback` | Rollback a website to a previous deployment |
+| `capix_website_get` | Get a website project descriptor |
+| `capix_website_deployments` | List deployments for a website |
+| `capix_website_logs` | Inspect build/runtime logs for a website |
+| `capix_website_metrics` | Inspect request/bandwidth metrics for a website |
+| `capix_website_domain_add` | Add a custom domain to a website |
+| `capix_website_domain_verify` | Verify DNS ownership for a pending custom domain |
+| `capix_website_domain_remove` | Remove a custom domain from a website |
+| `capix_website_destroy` | Destroy a website and all its resources |
+
+## Configuration
+
+### Environment variables
+
+| Variable | Required | Description |
+|---|---|---|
+| `CAPIX_BASE_URL` | No | Capix network URL (default: `https://capix.network`) |
+| `CAPIX_API_KEY` | No* | Session token / API key (fallback when no OAuth) |
+| `CAPIX_REFRESH_TOKEN` | No* | OAuth refresh token for auto-discovery |
+| `CAPIX_PROJECT_ID` | No | Default project id for unscoped reads |
+| `CAPIX_OAUTH_CLIENT_ID` | No | OAuth client id (default: `capix-mcp`) |
+| `CAPIX_MCP_HTTP_PORT` | No | Port for the streamable HTTP transport |
+| `CAPIX_MCP_HTTP_TOKEN` | No | Bearer service token guarding the HTTP transport |
+
+\* At least one of `CAPIX_API_KEY`, `CAPIX_REFRESH_TOKEN`, or stored OAuth credentials (via `capix-mcp login`) is required for authenticated tool calls.
+
+## CLI commands
+
+```
+capix-mcp [server] [--http <port> [--token <token>]]   Run the MCP server
+capix-mcp doctor                                        Diagnose auth + tool inventory
+capix-mcp login [--device]                              Authenticate via OAuth PKCE
+capix-mcp logout                                        Revoke tokens + clear credentials
+capix-mcp --version                                     Print version and exit
+capix-mcp --health                                       Run a quick health check and exit
+capix-mcp --help                                        Show help
+```
+
+## Example workflow: private LLM for a coding session
+
+```bash
+# 1. Authenticate
+capix-mcp login
+
+# 2. Your AI agent can now (autonomously):
+#    - Browse the model catalog
+#    - Find a GPU that fits the model's VRAM requirements
+#    - Deploy + wait for the endpoint to be ready
+#    - Use the endpoint as its LLM for the coding session
+#    - Destroy the instance when done to stop billing
+```
+
+The agent follows the Capix control-plane invariants:
+1. Read-only tools auto-run after authentication
+2. Billable tools require a bound `approvalToken` (obtained after quoting)
+3. Every billable action produces a work receipt with a cost breakdown
+
+## Auto-discovery in CapixIDE and Capix Code
+
+When you're signed in to CapixIDE or Capix Code, the IDE automatically:
+
+1. Spawns `capix-mcp` as a local MCP server
+2. Sets `CAPIX_REFRESH_TOKEN` in the server's environment
+3. The server uses the refresh token to obtain a fresh access token via the broker
+
+No manual configuration needed. Verify with:
+
+```bash
+capix-mcp doctor
+```
+
+## API reference
+
+Full API documentation: [https://capix.network/docs/api](https://capix.network/docs/api)
+
+## License
+
+Apache-2.0. See [LICENSE](LICENSE).
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md).
+
+## Links
+
+- **Capix Protocol** — [capix.network](https://capix.network)
+- **Capix IDE** — [github.com/CapIX-Protocol/CapIX-IDE](https://github.com/CapIX-Protocol/CapIX-IDE)
+- **Capix Code** (CLI assistant) — [github.com/CapIX-Protocol/CapIX-Code](https://github.com/CapIX-Protocol/CapIX-Code)
+- **MCP Protocol** — [modelcontextprotocol.io](https://modelcontextprotocol.io)

package/bin/capix-mcp.js

@@ -0,0 +1,2 @@
+#!/usr/bin/env node
+import('../dist/index.js');