@topolo/mcp 0.11.0 → 0.11.2

package/README.md

@@ -116,10 +116,18 @@ deletion, encryption, and audit storage for the data they own.
 | `topolo_whoami`              | (none)                | no               |
 | `topolo_search_applications` | (none)                | no               |
 | `topolo_get_application`     | (none)                | no               |
+| `topolo_get_resource_types`  | credential-scoped     | no               |
+| `topolo_list_resources`      | credential-scoped     | no               |
 | `topolo_search_actions`      | (credential-scoped)   | no               |
+| `topolo_discover_capabilities` | credential-scoped   | no               |
 | `topolo_get_action`          | (credential-scoped)   | no               |
+| `topolo_get_action_examples` | credential-scoped     | no               |
+| `topolo_validate_action`     | credential-scoped     | no               |
+| `topolo_plan_action`         | credential-scoped     | no               |
+| `topolo_prepare_action`      | credential-scoped     | no               |
 | `topolo_read_action`         | catalog or target policy | no            |
 | `topolo_call_action`         | catalog or target policy | yes           |
+| `topolo_upload_action`       | catalog or target policy | yes           |
 | `topolo_list_workspaces`     | target app runtime policy | no            |
 | `topolo_create_workspace`    | target app runtime policy | yes           |
 | `topolo_rename_workspace`    | target app runtime policy | yes           |
@@ -208,54 +216,4 @@ sent.
   disagrees with startup introspection (rare, but possible across scope
   changes). Re-spawn the server to refresh the cached scope set.
 
-## Development
-
-```bash
-cd TopoloMCP
-npm install
-npm run build
-TOPOLO_API_KEY=topo_live_... node dist/index.js
-```
-
-The server speaks MCP over stdio; when running standalone it just blocks
-waiting for JSON-RPC on stdin. To drive it manually, use the MCP Inspector:
-
-```bash
-npx @modelcontextprotocol/inspector node dist/index.js
-```
-
-## Release Flow
-
-Agent packages are released locally from the `staging` branch after its package
-gates pass. Publish in dependency order (`@topolo/sdk`, `@topolo/cli`, then
-`@topolo/mcp`) so every public dependency already exists in the registry.
-
-For each package, run its tests, typecheck, build, and tarball verification:
-
-```bash
-pnpm --dir packages/topolo-mcp test
-pnpm --dir packages/topolo-mcp typecheck
-pnpm --dir packages/topolo-mcp build
-node tooling/verify-npm-package.mjs packages/topolo-mcp
-```
-
-The npm token is stored in the macOS Keychain under `registry.npmjs.org`. Use a
-temporary npm config so the token is never written into the repository or
-printed:
-
-```bash
-printf '//registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}\n' > /tmp/topolo-release.npmrc
-NODE_AUTH_TOKEN="$(security find-generic-password -s registry.npmjs.org -w)" \
-  NPM_CONFIG_USERCONFIG=/tmp/topolo-release.npmrc \
-  sh -c 'cd packages/topolo-mcp && npm publish --access public'
-```
-
-After publishing, install exact versions into an empty temporary directory and
-exercise the SDK exports, CLI version command, MCP exports, and `topolo-mcp`
-executable before updating `topoloPublishedVersion`.
-
-## Phase 2 (planned)
-
-- Hosted action catalog administration in Developers UI.
-- HTTP transport in addition to stdio, for hosted (non-subprocess) deployments.
 - Optional `--provenance` on npm publish once the repo is public.