CoworkingView
com.coworkingview/mcp · 0.3.0
Search real coworking spaces in Europe and the Middle East: prices, amenities, locations.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://mcp.coworkingview.com/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 10 tools.
- Protocol
- 2025-06-18
- Calls itself
- coworkingview 0.3.0
- Handshake time
- 407 ms
- HTTP status
- 200
The tools it lists (10, as of 5 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
list_coworking_locationsLists every country, city and zone where CoworkingView has coworking spaces, with the exact slugs required by the other tools and how many spaces each place has. A "zone" is a district inside a city (for example "mitte" inside "berlin"). Call this before searching whenever the user names a place, because every filter takes a lowercase slug and a guessed slug returns an empty result rather than an error. Also answers "which cities do you cover?" directly.
resolve_coworking_queryTurns free text the user typed — a city, a district, an operator or brand name, or a specific building — into the exact slug and dimension the search tool needs. Returns each match with its `kind`, which tells you WHICH filter to use: a "city" or "zone" match goes in the `city`/`zone` argument, an "operator" match goes in `operator`, and a "property" match should be looked up directly with get_coworking_space. Use this whenever the user names something you do not already have a slug for.
get_coworking_filter_optionsReturns the exact values accepted by the filters of search_coworking_spaces — amenity slugs, workspace types, operators and the observed price and capacity ranges — each with the number of spaces it would match in the current context. Amenity slugs use underscores, for example "ac_heating" and "free_coffee_tea", and cannot be guessed reliably, so call this before filtering by amenity. Pass a city to get counts and ranges for that city rather than the whole catalogue.
search_coworking_spacesUse this whenever the user wants a coworking space, private office, serviced/managed office, team office, dedicated or hot desk, meeting room, day pass or virtual office in a city — in any language ("Büro mieten in Berlin", "oficina privada en Madrid", "flex office London"). Searches CoworkingView for coworking spaces and returns matching spaces with their "from" price, capacity, amenities, rating and a canonical URL to show the user. Filters take lowercase slugs, never display names: resolve a place with list_coworking_locations or resolve_coworking_query first, and get amenity slugs from get
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.coworkingview/mcp, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 59 days ago. The registry entry · coworkingview.com