Docs / Claude Code
Claude Code
VibeWorks is an MCP server. Claude Code (or any other MCP client) works directly with your projects, tasks, notes and docs – with your permissions.
Setup
- In VibeWorks, create a key under My account → Claude Code & API keys.
- Run the one-liner shown (Linux/macOS or Windows) in a terminal – it adds VibeWorks to Claude Code and saves the agent rules as a skill. By hand, the command looks like this:
claude mcp add --scope user --transport http vibeworks https://vibeworks.example.com/api/mcp --header "Authorization: Bearer vw_…"With --scope user the connection applies in all your repositories. Other MCP clients connect to /api/mcp via Streamable HTTP with the same header. Keys can be revoked any time; only a hash is stored.
With a device code
AI programs with device sign-in show a code and the address /verbinden. Sign in there, enter the code, check what the program may use and allow it – no key to copy. Codes are valid for 10 minutes.
Project keys
A key can be limited to selected projects, with an expiry date and a pause button. On the project page under Project keys you see who has access and revoke it one by one. Team members with the Grant project keys permission can do that too.
What Claude can do with it
| Tool | What it does |
|---|---|
list_projects, get_project | Projects with status, open tasks, notes and repository |
list_tasks, get_task | Tasks across all projects – e.g. everything due this week |
create_task, update_task | Create tasks and move them to “In progress” or “Done” – issues follow |
create_task_in_projects | The same task in several projects, by default in all linked to Git |
list_task_comments, add_task_comment | Read the conversation under an issue and reply |
update_project, review_projects | Status, priority, progress, summary – and an overview of what's missing |
get_project_structure, update_project_structure | A table of how the project is built |
list_workflows, start_workflow, complete_workflow_step, save_workflow | AI workflows step by step with verification |
get_ci, save_ci, run_ci | Read, change and start the CI pipeline |
list_code_files, search_code, get_code_graph, add_code_memo, delete_code_memo | Search code, see connections, leave notes on code |
create_note, get_note | Notes on a project, e.g. a work log |
search | Full-text search across notes, tasks and docs |
list_docs, get_doc, create_doc, update_doc | Read and write docs |
get_claude_md, get_agent_file, list_prompts, get_prompt | Instructions for the AI and your prompt library |
get_repo_status, list_problems | A repository's state (commits, CI, dependencies, repo check, live site) and everything that needs attention |
list_errors, resolve_error | Read errors from the error inbox with stack traces and tick them off after fixing |
get_today, add_to_today, remove_from_today | Plan the day – picked tasks and suggestions |
start_timer, stop_timer | Track time on a task, also as a focus timer |
Try: “Which tasks are open in VibeWorks?” or “Work through the open tasks of project X and write down what you did as a note.” Every change shows up in the project's activity log.
AI workflows
Project page → AI workflows: checklists the AI works through step by step – each step verified before the next one. Built in are “Implement feature”, “Fix bug”, “Prepare release”, “Review project” and “Maintain project structure”; add your own. While a workflow runs, VibeWorks reminds the AI of the next step on every call. In Claude Code the workflows are available as commands, too.
Project structure
Project page → Structure: a table with area, path, purpose and how it works. The AI creates it with update_project_structure and keeps it current; VibeWorks flags paths that no longer exist in the repository and writes the table into the instructions.
Instructions for the AI
Project → More actions → Generate AI instructions: description, status, open tasks, pinned notes, project structure and how to work with VibeWorks in one file – as CLAUDE.md, AGENTS.md (Codex and others), GEMINI.md, or a Copilot, Cursor, Windsurf or Cline rule. Adjust, copy or download it and put it in the repository – the AI reads it on every start.
Prompt library
Under Prompts you collect proven instructions. Placeholders like {{project}}, {{repo}}, {{live}} and {{summary}} are filled in by a chosen project when copying. “Add examples” creates five templates – from code review to “Work through open tasks”.