Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@WBSO MCP Server analyze my latest commit for WBSO relevance"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Generic MCP (Model Context Protocol) server for WBSO R&D documentation and time tracking. Enables AI assistants like Claude Code to automatically detect WBSO-relevant work and log entries.
WBSO Detection - Analyze commits, code, and work descriptions for WBSO eligibility
Work Classification - Classify work into technical challenge areas
Automatic Logging - Log research and development entries to documentation
Multi-year Support - Track hours across multiple WBSO project years
Configurable - Define your own technical challenges and keywords
Related MCP server: timecamp-mcp-server
git clone https://github.com/rubenmaas/wbso-mcp-server.git
cd wbso-mcp-server
npm installThe server loads project configuration from wbso.config.json in your WBSO documentation directory.
Copy the example config:
cp wbso.config.example.json /path/to/your/wbso-docs/wbso.config.jsonEdit the config with your project details:
{
"project": {
"name": "Your Project Name",
"projectNumber": "2025-1",
"company": "Your Company B.V."
},
"years": {
"2025": {
"totalHours": 1000,
"type": "New project"
}
},
"technicalChallenges": [
{
"id": "challenge-1",
"name": "Challenge Name",
"keywords": ["keyword1", "keyword2"],
"researchLogs": ["research-log"],
"devLogs": ["dev-log"]
}
]
}Add to your Claude Code config (~/.claude/claude_desktop_config.json):
{
"mcpServers": {
"wbso": {
"command": "node",
"args": ["/path/to/wbso-mcp-server/index.js"],
"env": {
"WBSO_DIR": "/path/to/your/wbso-docs"
}
}
}
}Tool | Description |
| Analyze if code/commits are WBSO-relevant |
| Classify work into technical challenge areas |
| Check if a git commit qualifies as WBSO work |
| Get full project criteria and challenges |
Tool | Description |
| Log research entries to documentation |
| Log development entries to documentation |
| Log time entries for the current week |
| Get current WBSO hours status |
{
"project": {
"name": "Project Name",
"projectNumber": "2025-1",
"company": "Company B.V."
}
}{
"years": {
"2025": {
"applicationNumber": "SO25XXXXXX",
"period": "January - December 2025",
"totalHours": 1000,
"type": "New project"
}
}
}{
"technicalChallenges": [
{
"id": "unique-id",
"name": "Challenge Name",
"description": "Description of technical uncertainty",
"keywords": ["keyword1", "keyword2"],
"filePatterns": ["pattern1", "pattern2"],
"researchLogs": ["log-name"],
"devLogs": ["log-name"]
}
]
}{
"relevantPaths": ["service", "repository", "controller"],
"excludePatterns": ["node_modules", "vendor", "\\.lock$"]
}Variable | Description | Default |
| Path to WBSO documentation directory | Current working directory |
MIT
Analyze whether code, commits, or work description is relevant to the WBSO project.
Inputs: content (required), diff, files_changed.
Check if a git commit should be logged as WBSO work
Inputs: commit_hash, repository_path.
Classify work into the appropriate WBSO technical challenge area
Inputs: description (required), filename.
Get the full WBSO project criteria and technical challenges
Inputs: no named parameters.
Get current WBSO documentation status
Inputs: no named parameters.
Log a development entry to WBSO documentation
Inputs: hours (required), results (required), log_name (required), technical_challenge (required), +6 more.
Log a research entry to WBSO documentation
Inputs: hours (required), findings (required), log_name (required), technical_uncertainty (required), +3 more.
Log time spent on WBSO R&D work
Inputs: hours (required), description (required), activity_type (required), jira_ref.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 8 tools
The tools analyze_wbso_relevance, classify_work, and check_commit_wbso all serve to determine whether work qualifies as WBSO and how to categorize it, creating significant overlap. While descriptions differ slightly (relevance check, classification, commit-specific check), an agent could easily misselect among them.
All tool names follow a snake_case verb_noun pattern (analyze_, classify_, check_, get_, log_), which is consistent. Minor inconsistency exists in whether 'wbso' appears in the noun part (analyze_wbso_relevance, get_wbso_criteria vs. classify_work, log_time), but overall the pattern is clear and predictable.
With 8 tools, the server is well-scoped for WBSO management, covering analysis, classification, logging, and status retrieval without unnecessary redundancy. The number feels appropriate for the domain and each tool appears to contribute to the workflow.
The tool set covers the core WBSO workflow: checking relevance, classifying work, logging research/development/time, and viewing criteria/status. Minor gaps exist—such as no update or delete operations for logged entries—but for the apparent purpose of documentation and tracking, the surface is reasonably complete.
Time tracking you talk to: log, check and fix your work hours from your AI assistant.
Connects AI assistants to TrackingTime for querying time entries, projects, tasks, customers, and team data using natural language.
Log hours and invoice clients from your AI chat. Time tracking and invoicing for freelancers.
Privacy-first work tracking with summaries, reports, coaching, and AI-ready long-term memory.
