Semrush AppCenter MCP Server
Base URL: https://api.semrush.com
| Category | Developer Tools |
| Tools | 4 |
| Auth | JWT |
Install
Quick Start (recommended)
JWT_SHARED_SECRET=YOUR_JWT_SHARED_SECRET \
JWT_ISSUER_ID=YOUR_JWT_ISSUER_ID \
uvx mcparmory-semrush-appcenter
With pip
pip install mcparmory-semrush-appcenter
JWT_SHARED_SECRET=YOUR_JWT_SHARED_SECRET \
JWT_ISSUER_ID=YOUR_JWT_ISSUER_ID \
mcparmory-semrush-appcenter
MCP Client Configuration
Add to your MCP client config (e.g. Claude Desktop, Cursor, Codex):
{
"mcpServers": {
"semrush-appcenter": {
"command": "uvx",
"args": ["mcparmory-semrush-appcenter"],
"env": {
"JWT_SHARED_SECRET": "YOUR_JWT_SHARED_SECRET",
"JWT_ISSUER_ID": "YOUR_JWT_ISSUER_ID"
}
}
}
}
Credentials
Set the following environment variables (via MCP client env config, shell export, or .env file):
JWT_SHARED_SECRET— Shared JWT signing secretJWT_ISSUER_ID— Issuer ID (App ID, Team ID, etc.)
Do not commit credentials to version control.
JWT Bearer
This server uses JWT Bearer authentication — tokens are generated automatically from signing material configured in .env.
Depending on the provider, set either:
JWT_PRIVATE_KEYto either:- File path:
/path/to/private-key.pem - Inline PEM: paste the full PEM content with newlines replaced by
\n JWT_SHARED_SECRETto the shared secret used to sign the JWT
Set JWT_ISSUER_ID to the application/issuer ID provided by the API (e.g. GitHub App ID).
Optional settings (see .env for details): algorithm, expiry (default 600s), audience, key ID, token exchange URL.
Run Locally
First, configure your credentials in .env (see Credentials above).
pip install -r requirements.txt
python server.py
Connect MCP Client
Edit .mcp.json and replace <SERVER_DIR> with the absolute path to this directory, then add to your MCP client configuration.
Example (if server is at /home/user/mcp-servers/semrush-appcenter):
{
"mcpServers": {
"semrush-appcenter": {
"command": "python",
"args": ["/home/user/mcp-servers/semrush-appcenter/server.py"]
}
}
}
Docker
Pre-built image (recommended)
docker run -p 8000:8000 \
-e JWT_SHARED_SECRET=YOUR_JWT_SHARED_SECRET \
-e JWT_ISSUER_ID=YOUR_JWT_ISSUER_ID \
ghcr.io/mcparmory/semrush-appcenter:latest
Build from source
First, configure your credentials in .env (see Credentials above).
docker build -t semrush-appcenter .
docker run -p 8000:8000 --env-file .env semrush-appcenter
Before running, make sure ports 8000 are free.### MCP client config (Docker)
For Docker, use SSE transport in your MCP client config:
{
"mcpServers": {
"semrush-appcenter": {
"type": "sse",
"url": "http://localhost:8000/sse"
}
}
}
Files
.env- Credentials and server configuration.mcp.json- MCP client config templateDockerfile- Container buildLICENSE- MIT license for this generated coderequirements.txt- Python dependenciesREADME.md- This fileserver.py- MCP server entry point_auth.py- Authentication handlers_models.py- Request/response models_validators.py- Input validation
Note: Files starting with . are hidden by default on macOS/Linux. Use ls -a in terminal or enable "Show hidden files" in your file manager to see .env and .mcp.json.
Generated by MCP Blacksmith · Quickstart docs · Report a bug
Metadata
Release files for mcparmory-semrush-appcenter 1.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mcparmory_semrush_appcenter-1.0.2-py3-none-any.whl | Python 3 | none | any | Details for mcparmory_semrush_appcenter-1.0.2-py3-none-any.whl |
Release files / mcparmory_semrush_appcenter-1.0.2-py3-none-any.whl
| Download URL | mcparmory_semrush_appcenter-1.0.2-py3-none-any.whl |
|---|---|
| Size | 37.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f6083afeb89a031ef6b1554bc19a9088239c1f8f06cf56b6f52f6c21ce7969f0
|
|
BLAKE2b-256 checksum How to use checksums |
5a915cbb10d9e2cdc7931b809d7f3ead8015b0c3dafe42f1874beeb31f22d5ae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for mcparmory-semrush-appcenter 1.0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.