About Pushinator MCP
Pushinator MCP is an MCP server for connecting an MCP client to Pushinator. The provided setup uses a Pushinator API token supplied through the `PUSHINATOR_API_KEY` environment variable.
Key features
- 01Connects an MCP client to Pushinator
- 02Uses a Pushinator API token
- 03Configures the token through an environment variable
Use cases
- 01Set up Pushinator in an MCP client
- 02Provide a Pushinator API token to the server
MCP support
The server can be added to an MCP client's configuration and runs from the built `build/index.js` file. The README does not describe its exposed tools.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEPushinator MCP
To install dependencies:
bun install
To build:
bun run build
After that, add the Pushinator MCP to your MCP client (the API token can be retrieved in your Pushinator API tokens page):
{
"mcpServers": {
"pushinator": {
"command": "node",
"args": ["path-to-repo/build/index.js"],
"env": {
"PUSHINATOR_API_KEY": "YOUR_PUSHINATOR_API_KEY"
}
}
}
}
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.