search_posts
Search Discourse posts
Search the posts on a Discourse forum from an agent session with one call that takes a query.
LABSCO SUMMARY
search_posts takes a query and nothing else, so there is no filtering by category, author or date at the call — the shaping has to live in the query string itself. Topics, users and anything that writes to the forum sit outside this surface; credentials are still required because the search runs as a Discourse API user.
A search front end for a Discourse instance, exposing search_posts as its whole surface.
A Discourse instance reachable at DISCOURSE_API_URL, with an API key in DISCOURSE_API_KEY and the API username it acts as in DISCOURSE_API_USERNAME.
One command plus a key — npx -y @ashdev/discourse-mcp-server, then supply credentials
USE CASES
Put the question to the Discourse instance as a query and read back the posts that match, before answering from anywhere else.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
search_postsSearch Discourse posts
BEFORE YOU INSTALL
1 tool when we connected. search_posts only reads; there is no tool to post or reply.
Both documented setups run the server on your machine.
CONTEXT COST
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
npx -y @ashdev/discourse-mcp-server{
"mcpServers": {
"discourse": {
"command": "npx",
"args": [
"-y",
"@ashdev/discourse-mcp-server"
],
"env": {
"DISCOURSE_API_URL": "https://try.discourse.org",
"DISCOURSE_API_KEY": "1234",
"DISCOURSE_API_USERNAME": "ash"
}
}
}
}{
"mcpServers": {
"discourse": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"DISCOURSE_API_URL=https://try.discourse.org",
"-e",
"DISCOURSE_API_KEY=1234",
"-e",
"DISCOURSE_API_USERNAME=ash",
"ashdev/discourse-mcp-server"
]
}
}
}