VTC Spaces

com.vtc/mcp · v0.5.1 · agents-and-memory

VTC Spaces is healthy: it completed an MCP handshake in 10042 ms and exposes 29 tools.

Search public VTC Spaces and people; sign in to query Space data and run AI actions and workflows.

Endpoint: https://mcp.vtc.com/mcp (streamable-http)

No repository listed · Website · JSON · Add to my inventory

Facts

Users (last 30 days)	0
Handshake	Healthy
Auth needed	None
Tool count	29
Latency	10042 ms
Last checked (UTC)	2026-10-22T04:40:23.143Z

Health history

Checked (UTC)	Status	Latency	Error
2026-10-22T04:40:23.143Z	Healthy	10042

Tools (29)

`login_with_otp`	Start ZAPI OTP login for an existing account. Then call verify_otp with the code and space group_id. Prefer explain_space_context after auth before querying.
`verify_otp`	Complete OTP login and store a space-scoped JWT in memory only (not on disk). group_id is required for Shared space DB access.
`validate_jwt`	Decode the current session JWT claims (no signature verify — ZAPI verifies on /db/).
`set_session_jwt`	Set/replace the in-memory JWT (space-scoped token from the app). Prefer OTP for interactive use. JWT is never written to disk.
`explain_space_context`	Call this first after auth. Summarizes environment, group_id, user, and role so you do not query the wrong Space or live vs beta.
`search_public`	Search public people by username, and public spaces or networks by name or username (no login). Networks are spaces with kind "network". Use a space or network id with set_guest_context.
`search_public_spaces`	Find public VTC Spaces by space name or space username/slug (no login). Use the returned id with set_guest_context.
`search_public_people`	Find public people by username (optional leading @). No login. People who opted out of search, or who are only in a private network, are omitted. Email is not searchable.
`set_guest_context`	Bind a Space for guest/public tools (no login). Accepts a numeric id, public slug (dexi), or a name that matches one public space. Prefer search_public_spaces when the name may match several spaces.
`list_guest_public_apps`	List apps on a Space dashboard that allow guest browse (public_guest_access=yes). Uses public ZAPI — no Space JWT.
`describe_public_app_surface`	AI manifest plus guest/public read hints for one app (module_code). No Space JWT required.
`list_public_collection_documents`	Read documents from a collection the Space marked public-read (ZAPI). No JWT.
`fetch_app_public_route`	GET an allowlisted HTTPS public API URL on *.apps.vtc.com (path must include /public). No JWT.
`space_db_info`	Call after auth (and ideally after explain_space_context). Resolves the current Shared space silo via ZAPI (URI redacted). Does not accept group_id — silo is always the JWT space.
`list_collections`	List collections in the authenticated space silo (excludes system.*). Call this before assuming collection names. Use include_counts sparingly.
`count_documents`	Count documents with an optional filter. Soft-deleted rows (status=deleted) are excluded by default when the collection has status — set include_deleted=true to override.
`find_documents`	Find documents (max 50, skip capped). Prefer narrow filter + projection. Call list_collections and sample_document before guessing schema. Soft-deletes excluded by default; sensitive fields redacted by default.
`sample_document`	Return one document for schema inference. Sensitive fields are redacted by default. Prefer this before large finds.
`list_developer_catalog`	Public ZAPI developer catalog of app-facing API services (no auth). Use when discovering platform endpoints for child apps — not for Space Mongo data.
`list_space_apps`	List apps installed / owned in the authenticated Space (JWT group_id). Call explain_space_context first. Not a Mongo query.
`get_ai_manifest`	Fetch the AI tool manifest for a module_code (installed app). Use after list_space_apps when you need tool schemas — not for inspecting Mongo collections.
`get_space_summary`	Lightweight summary of the authenticated Space from JWT claims (group_id, network_id, role). Does not query Mongo. Prefer this or explain_space_context before DB tools.
`list_available_actions`	List AI Guide tools the current JWT may run (default: platform.* only). Opt into installed app manifests with include_apps or VTC_MCP_ACTION_MODULES. Call explain_space_context first. Does not execute anything.
`execute_action`	Execute an AI Guide tool via ZAPI /ai/tools/execute (same path as in-product Guide). For confirm_required tools: first call WITHOUT confirmation_token returns a proposal; second call WITH confirmation_token performs the action. Read-only tools (confirm_required=false) run immediately. Do not set con
`list_workflows`	List saved workflows in the authenticated Space. Call explain_space_context first. Read-only.
`get_workflow`	Fetch one space workflow by id (steps, trigger, gaps). Read-only.
`propose_workflow`	Draft a workflow from natural language via ZAPI /ai/propose-workflow. Does not persist — review then save_workflow. Prefer this over inventing step schemas.
`save_workflow`	Create a workflow in the Space (space admin JWT). First call returns confirmation_token; second call with that token persists. Defaults automation_enabled to false unless you set true explicitly. Does not use /ai/execute-agent.
`run_workflow`	Run a saved workflow. dry_run=true (default) previews without side effects. dry_run=false requires confirmation_token from a prior proposal. Does not call /ai/execute-agent.