WeWork MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WEWORK_ACCESS_TOKEN | Yes | Your WeWork API access token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_projectsB | |
| get_project_detailsB | |
| analyze_project_tasksC | |
| find_project_by_nameB | |
| get_project_statisticsC | |
| test_connectionB | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| file://projects/available |
TDQS
Scored across 6 tools
Most tools have distinct purposes: analyze_project_tasks focuses on task analysis, find_project_by_name and search_projects handle project discovery (though these two could be confused), get_project_details and get_project_statistics provide different project information, and test_connection is clearly separate. The main ambiguity is between find_project_by_name and search_projects, which both search projects by name with slightly different approaches.
Tool names follow a consistent snake_case pattern with clear verb_noun structure (analyze_project_tasks, find_project_by_name, get_project_details, etc.). The only minor deviation is test_connection, which uses a simpler verb_noun pattern but still fits the overall naming convention.
With 6 tools, this is well-scoped for a project management server focused on WeWork. The count is appropriate as it covers core operations (project discovery, details, statistics, task analysis) without being overwhelming or too sparse for the domain.
The toolset covers project discovery and analysis well but has notable gaps in project lifecycle management. There are no tools for creating, updating, or deleting projects or tasks, which limits agents to read-only operations. However, for analysis and monitoring purposes, the existing tools provide reasonable coverage.