Contextium MCP Server vs Workspace Qdrant MCP

list

List all resources of a given type in a workspace — the fast way to see what already exists before you act. Returns lightweight summaries (IDs, names, key fields), not full content: use `get` for one resource's full detail, or `search` to find resources by text or tag. Set `type` to choose what to list — workspaces, libraries (context libraries), agents, skills, files (pass libraryId), workflows, tags, file_tags (pass fileId), workspace_status, or members (with roles + activity). Uses your active workspace when workspaceId is omitted.

get

Get full details of a resource by ID. Use workspace_activity for recent activity logs. Use activity_archive to read a specific month's archived logs by YYYY-MM (e.g. 2025-02). Use list_activity_archives to see which months have archives. Use workflow_activity for the activity digest since a workflow's last session. Use entity_activity for recent activity on a specific file or entity.

create

Create a new resource in a workspace. Set `type` to what you're creating: "file" (needs libraryId + title + complete content), "library" (a context library — needs name), or "agent" / "skill" / "workflow" (need name; a workflow can bundle projectIds, agentIds, skillIds, and tagIds). Always provide full, real content for files — never empty or placeholder. File linking: to link to another file in the SAME workspace, put //<fileId> inline in the content — use the target file's UUID (from search/list/get results), not its title. The link renders as the target's title and is indexed automatically on save; the target gains a backlink with no extra step. Add a link only where the text genuinely references an existing file; never invent //<id> for a file that does not exist (it becomes a dangling link). Use get({ type: "file_links", id }) to inspect a file's links and backlinks.