The hosted Silverile MCP server exposes stories, defects, sprints, test cases, and project workflows to MCP-compatible clients through Streamable HTTP.
Ask your AI assistant things like:
| What you can say | What happens |
|---|---|
| Check that my connection is working | Validates the OAuth credential 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 future sessions |
| Show me the details for story 837 | Returns the description, acceptance criteria, status, and assignee |
| What am I working on? | Returns the stories and defects currently assigned to you |
| Create a new story for user login | Shows a preview and asks for confirmation before saving |
Configure your client with only the production MCP endpoint:
https://mcp.silverile.com/mcp
Then use the client's Authenticate, Connect, or OAuth login action. The browser opens the Silverile sign-in page (Keycloak); sign in with your existing Silverile account to authorize the connection.
No API key or secret goes into the MCP client configuration. After sign-in the client receives an OAuth access token and a rotating refresh token; Keycloak controls their lifetimes, and compatible clients refresh the access token automatically.
On first connect Monty uses your Silverile default project. To pin a different one, tell Monty "set project 12 as my default" — it is remembered across sessions.
Authorization header unless Silverile support explicitly directs you to a separate service-to-service integration.After authentication, ask:
The client should call validate_connection and report the active project.
"Unauthorized" or 401 during the first MCP request
An initial unauthenticated request is expected for OAuth discovery. Use the client’s Authenticate or Connect action and complete the Silverile authorization page.
401 after authentication
Disconnect or log out only the Silverile MCP connection, then authenticate again. Confirm your Silverile account still has access to the workspace.
"Unknown OAuth client or unregistered redirect_uri"
The client is reusing an obsolete OAuth registration. Delete and recreate the Silverile MCP connection, then authenticate again.
The client asks for a bearer token or custom Authorization header
Do not generate a base64 bearer token or set a custom Authorization header. Configure the HTTPS MCP URL only, and use the client’s OAuth Authenticate or Connect action.
Tools are missing after authentication
Restart or refresh the MCP client after login so it performs a new initialize and tools/list request with the OAuth access token.