Fetch usecase

Add MCP server to your AI tool

Allow AI tools and LLMs to interact with the API documentation portal through MCP.

MCP server URL


        
          
            https://twilio.demo.bump-doc.com/doc/messaging_v1/mcp

Standard setup for AI tools providing an mcp.json file

      
          mcp.json

"messaging_v1 MCP server": {
  "url": "https://twilio.demo.bump-doc.com/doc/messaging_v1/mcp"
}

GET /v1/Services/Usecases

Account sid auth token

Use Case resource. Fetch possible use cases for a Messaging Service.

Responses

200 application/json

OK
Hide headers attributes Show headers attributes
- Access-Control-Allow-Origin string
  
  Specify the origin(s) allowed to access the resource
- Access-Control-Allow-Methods string
  
  Specify the HTTP methods allowed when accessing the resource
- Access-Control-Allow-Headers string
  
  Specify the headers allowed when accessing the resource
- Access-Control-Allow-Credentials boolean
  
  Indicates whether the browser should include credentials
- Access-Control-Expose-Headers string
  
  Headers exposed to the client
Hide response attribute Show response attribute object
- usecases array | null
  
  Human readable use case details (usecase, description and purpose) of Messaging Service Use Cases.

GET /v1/Services/Usecases

curl \
 --request GET 'https://messaging.twilio.com/v1/Services/Usecases' \
 --user "username:password"

Response examples (200)

{
  "usecases": [
    {
      "usecase": "notifications",
      "description": "Transactional notifications and Alerts for any Delivery, Account, Reminder, Order, Fraud, Security, Public Service, or Emergency announcements.",
      "purpose": "Notify my users."
    },
    {
      "usecase": "marketing",
      "description": "Marketing messages may contain product information, offers, and calls to action to engage with your organization.",
      "purpose": "Market my services."
    }
  ]
}