Install
$ agentstack add skill-rasahq-rasa-agent-skills-rasa-configuring-mcp-server ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Configuring MCP Servers
MCP servers expose external tools — APIs, databases, services — to a Rasa assistant. All MCP servers are defined in endpoints.yml and shared across direct flow tool calls and ReAct sub agents.
This feature is in beta and available starting from Rasa 3.14.0.
Workflow
- Add each MCP server to
endpoints.yml(see "Server definition"). - Add authentication if the server requires it (see "Authentication").
- Validate the project.
Server definition
Register every MCP server in endpoints.yml.
| Key | Required | Description | |--------|----------|-------------| | name | yes | Unique identifier — referenced from flows and sub agent configs. Duplicates cause a validation error at startup | | url | yes | URL where the MCP server is running | | type | yes | http or https |
# endpoints.yml
mcp_servers:
- name: trade_server
url: http://localhost:8080
type: http
- name: payment_server
url: https://api.payment-service.com
type: https
Authentication
Add auth fields directly to the server entry in endpoints.yml when the MCP server requires credentials. Sensitive values (api_key, token, client_secret) must use ${ENV_VAR} syntax — plain text is rejected by validation.
API key
Sent as Authorization: Bearer by default. Add header_name and header_format to override the header.
mcp_servers:
- name: secure_api_server
url: https://api.example.com
type: https
api_key: "${API_KEY}"
header_name: "X-API-Key" # optional, default: Authorization
header_format: "{key}" # optional, default: Bearer {key}
OAuth 2.0 (client credentials)
mcp_servers:
- name: oauth_server
url: https://api.example.com
type: https
oauth:
client_id: "${CLIENT_ID}"
client_secret: "${CLIENT_SECRET}"
token_url: "https://auth.example.com/oauth/token"
scope: "read:data write:data" # optional
audience: "https://api.example.com" # optional
timeout: 10 # optional
Pre-issued token
mcp_servers:
- name: token_server
url: https://api.example.com
type: https
token: "${ACCESS_TOKEN}"
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: RasaHQ
- Source: RasaHQ/rasa-agent-skills
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.