CohostSTR (MCP server for Guesty) runs on your own machine — the client starts it, so there is no endpoint to ping. 90 installs a week from npm. Last commit 25 Sep 2026.
CohostSTR: MCP server for Guesty. 43 read/write tools, free. Grounded replies, policy screen.
What the code does
We read the source, 6 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
ENV GUESTY_CLIENT_SECRET=""
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add cohoststr-mcp -e 'GUESTY_CLIENT_ID=<GUESTY_CLIENT_ID>' -e 'GUESTY_CLIENT_SECRET=<GUESTY_CLIENT_SECRET>' -- npx -y cohoststr-mcp{
"mcpServers": {
"cohoststr-mcp": {
"command": "npx",
"args": [
"-y",
"cohoststr-mcp"
],
"env": {
"GUESTY_CLIENT_ID": "<GUESTY_CLIENT_ID>",
"GUESTY_CLIENT_SECRET": "<GUESTY_CLIENT_SECRET>"
}
}
}
}[mcp_servers.cohoststr-mcp]
command = "npx"
args = ["-y", "cohoststr-mcp"]
env = { GUESTY_CLIENT_ID = "<GUESTY_CLIENT_ID>", GUESTY_CLIENT_SECRET = "<GUESTY_CLIENT_SECRET>" }{
"mcpServers": {
"cohoststr-mcp": {
"command": "npx",
"args": [
"-y",
"cohoststr-mcp"
],
"env": {
"GUESTY_CLIENT_ID": "<GUESTY_CLIENT_ID>",
"GUESTY_CLIENT_SECRET": "<GUESTY_CLIENT_SECRET>"
}
}
}
}{
"servers": {
"cohoststr-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"cohoststr-mcp"
],
"env": {
"GUESTY_CLIENT_ID": "<GUESTY_CLIENT_ID>",
"GUESTY_CLIENT_SECRET": "<GUESTY_CLIENT_SECRET>"
}
}
}
}Put your own values in place of
<GUESTY_CLIENT_ID> (Guesty OAuth2 Client ID), <GUESTY_CLIENT_SECRET> (Guesty OAuth2 Client Secret).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
GUESTY_MCP_LICENSE_KEY (Optional. All tools are currently free; a key is recognized but does not change access).
Alternatives to CohostSTR (MCP server for Guesty)
same job, measured the same wayYuque MCP server with safe read/write tools for groups, group members, repositories, docs, and TOC.
Unofficial local MCP server for Livespace CRM with read tools and guarded writes.
Policy-driven, read-only MCP server for safe database access from AI tools.
Google Search Console MCP server: 20 read tools, no write tools.
Adjust MCP server: 5 read tools, 0 write tools. Read-only reporting for allowlisted apps.
Google Analytics 4 MCP server: 27 read tools, no write tools.
Read-only evidence for the tools agents run: MCP server records, coverage and policy.
MCP server for accurate, structure-preserving read/write access to Excel (.xlsx) files
CohostSTR (MCP server for Guesty) — questions
Answers built from our own checks of this server.