- Home
- MCP servers
- WeWork
WeWork
- python
0
GitHub Stars
python
Language
7 months ago
First Indexed
3 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"fox2920-aplus-mcp": {
"command": "uv",
"args": [
"run",
"wework_mcp_server.py"
],
"env": {
"WEWORK_ACCESS_TOKEN": "YOUR_WEWORK_TOKEN"
}
}
}
}You can access WeWork project data, perform task analysis, and manage projects through an MCP server that exposes project information and analysis tools to Claude and other clients. This server lets you search projects, analyze tasks, track deadlines, and export data for reporting, all via MCP-compatible interfaces.
How to use
Connect your MCP client to the server to start exploring projects and task data. You can search for projects by name, analyze tasks within a project, view completion statistics, and export results to CSV. Use natural language prompts like "Show me all available projects" or "Analyze tasks for project ID 12345" to retrieve structured insights.
Practical usage patterns you can try:
- Search projects by name or with fuzzy matching to identify closely related projects
- Get detailed information for a specific project to review deadlines and statuses
- Run task analysis to see progress, categorization by status and assignee, and common failure reasons
- Export task analysis data to CSV for external reporting and sharing
How to install
# Prerequisites
- Python 3.12+
- WeWork API access token
- uv package manager
# Step 1: Clone the server repository
git clone <repository-url>
cd wework-mcp-server
# Step 2: Install dependencies
uv sync
# Step 3: Run the server locally (choose one)
uv run wework_mcp_server.py
# or
python wework_mcp_server.py
Local configuration and runtime options are shown below. Decide whether to supply tokens via environment variables or inline configuration, then start the server accordingly.
{
"mcpServers": {
"wework_local": {
"type": "stdio",
"name": "wework_local",
"command": "uv",
"args": ["run", "wework_mcp_server.py"]
},
"wework_local_python": {
"type": "stdio",
"name": "wework_local_python",
"command": "python",
"args": ["wework_mcp_server.py"]
}
},
"envVars": [
{
"name": "WEWORK_ACCESS_TOKEN",
"description": "WeWork API access token",
"required": true,
"example": "YOUR_WEWORK_TOKEN"
}
]
}
Local environment token can be provided via a .env file in the project root as shown below.
WEWORK_ACCESS_TOKEN=your_actual_wework_token_here
Available tools
search_projects
Search for projects by name with fuzzy matching to locate relevant projects.
find_project_by_name
Find a project using similarity matching to identify best matches.
get_project_details
Retrieve detailed information about a specific project, including deadlines and status.
analyze_project_tasks
Analyze tasks within a project, including categorization and completion progress.
get_project_statistics
Provide comprehensive statistics for a project, including progress and performance metrics.