Skip to main content
Glama
jjunmomo

BaaS SMS/MCP Server

by jjunmomo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_code_template_urlA
Get URL for BaaS SMS/MMS integration code template from CDN

Perfect for: Getting optimized, maintained code templates without token overhead

Args:
    language: Programming language (javascript, python, php, java, go, csharp)
    framework: Optional framework (react, vue, django, laravel, fastapi, spring, etc.)
    deployment_platform: Optional platform (vercel, netlify, aws, docker, etc.)

Returns:
    CDN URL to markdown file with complete code examples and integration guide
    Templates include direct API calls to https://api.aiapp.link with /api/message/ endpoints
generate_direct_api_codeA
Generate code that directly calls BaaS API by fetching templates from CDN

Perfect for: Production deployments, custom integrations, framework-specific implementations
Token-optimized: Fetches maintained templates from CDN instead of generating locally

Args:
    language: Programming language (javascript, python, php, java, go, csharp)
    framework: Optional framework (react, vue, django, laravel, fastapi, spring, etc.)
    include_examples: Include usage examples and configuration templates
    
Returns:
    Dictionary with code fetched from CDN, filename, and integration instructions
    Code directly calls https://api.aiapp.link/api/message/ with X-API-KEY header authentication
    If MCP server has BAAS_API_KEY set, it will be automatically injected into code
create_message_service_templateA
Create a complete message service template by fetching from CDN and customizing with project config

Perfect for: New project setup, team standardization, rapid prototyping
Token-optimized: Fetches base template from CDN then applies project customizations

Args:
    project_config: Project configuration {default_callback, company_name, etc.}
    language: Target programming language
    features: List of features to include ["sms", "mms", "status_check", "history", "validation"]
    
Returns:
    Complete service template with project-specific defaults and configuration
    Automatically injects BAAS_API_KEY from MCP server environment if available
get_integration_guideA
Get detailed integration guide by fetching from CDN for specific platforms and deployment scenarios

Perfect for: DevOps setup, deployment planning, team onboarding
Token-optimized: Fetches comprehensive guides from CDN instead of hardcoded responses

Args:
    platform: Target platform (vercel, netlify, heroku, aws, gcp, azure, docker, etc.)
    deployment_type: Deployment type (development, staging, production)
    
Returns:
    Step-by-step integration guide with platform-specific instructions fetched from CDN
    Updated for new /api/message/ endpoints and X-API-KEY authentication

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.1/5.0

Scored across 4 tools

Disambiguation4/5

The tools have distinct primary purposes: create_message_service_template for project setup, generate_direct_api_code for production code generation, get_code_template_url for template retrieval, and get_integration_guide for deployment guidance. However, there is some overlap between generate_direct_api_code and get_code_template_url, as both fetch code templates from CDN, which could cause minor confusion about which to use for code generation tasks.

Naming Consistency4/5

Tool names follow a consistent verb_noun pattern (e.g., create_message_service_template, get_integration_guide), making them predictable and readable. The only minor deviation is generate_direct_api_code, which uses 'generate' instead of 'create' or 'get', but this is acceptable given its distinct action.

Tool Count4/5

With 4 tools, the count is appropriate for a BaaS SMS/MCP server focused on code generation and integration. It covers key areas like template creation, code generation, and deployment guidance without being overly sparse or bloated. A slight expansion to include more CRUD operations (e.g., update or delete templates) could improve it, but it's reasonable as-is.

Completeness3/5

The toolset covers template creation, code generation, and integration guides, which aligns with a BaaS SMS domain for setup and deployment. However, there are notable gaps in lifecycle coverage, such as missing update or delete operations for templates, and no tools for actual SMS sending, status checking, or message history management, which are core to SMS services.

Resources