The Silverile MCP Server exposes your stories, backlog, and workspace as tools that any MCP-compatible client can call via Streamable HTTP transport.
Ask your AI assistant things like:
| What you can say | What happens |
|---|---|
| Check that my credentials are working | Validates your API key and confirms the server can reach Silverile |
| Show me my available projects | Lists all Silverile projects you have access to |
| Set project 12 as my default | Saves a project as the default for all future sessions |
| Clear my default project | Removes the saved default so you can pick a different project |
| Show me the details for story 837 | Returns the full description, acceptance criteria, status, and assignee for a story |
| List the stories in my project | Retrieves the story backlog for the active project |
| What am I working on? | Returns the stories currently assigned to you |
| Create a new story for user login | Creates a new story — shows a preview and asks for your confirmation before saving |
| Show me defect 2342 | Returns the full details for that specific defect |
| Show my defects | Retrieves open, in-progress, and re-opened defects with pagination |
ide_XXXXXXXXXXXXXXXX) and the Key SecretOpen your Silverile workspace. The URL contains your Product ID — for example, silverile.com/product/12/.... Note that number; you'll need it below.
For step-by-step client setup see:
"Unauthorized" or 401 errors
Your Key ID and Key Secret are case-sensitive. Confirm both are correct and that the key is still active under Settings → IDE API Keys in Silverile.
Empty story or defect list, or "product not found"
Check that the productId in your bearer token is a number (e.g. 12), not a name or slug. Regenerate the token if needed.
Bearer token rejected
The token must be URL-safe base64 (no padding, + and / replaced with - and _). Use the openssl pipeline in the integration guide to regenerate it.
HTTP mode returns 401 on all requests
The Bearer token must be base64url-encoded JSON containing keyId, keySecret, and productId. Confirm the encoding matches the format in the integration guides.