AT Bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| at_list_portsA | List all available COM/serial ports. Returns device name, description, hardware ID, VID/PID. |
| at_configureA | Configure serial port parameters (baud rate, data bits, parity, stop bits, flow control). Can be called before or after opening the port. |
| at_open_portB | Open the specified COM port and establish a serial connection. |
| at_close_portB | Close the currently opened COM port connection. |
| at_auto_detectA | Auto-detect all available COM ports. Tries common baud rates and sends an AT probe command to find responsive devices. Useful when unsure which port the device is connected to. |
| at_send_commandA | Send an AT command to the connected device and read the response. Auto-prepends AT prefix (e.g. 'CSQ' becomes 'AT+CSQ'). Supports standard AT and extended AT+ commands. |
| at_batch_testA | Batch-test AT commands. Sends a list of AT commands to the connected device and returns all results with automatic classification (PASS/OK/ERR/CME). Much more efficient than calling at_send_command repeatedly; good for validating a command list from the knowledge base. |
| at_knowledge_searchA | Search the AT command knowledge base. Supports filtering by keyword (key/name/description/AT string) and source (3gpp/vendor/custom). |
| at_knowledge_chipsetsA | List available chipset knowledge base files. AI should call this first to know which platforms exist, then use at_knowledge_add to write to the appropriate platform file. |
| at_knowledge_addA | Add or update an AT command in the knowledge base. Stores in the specified chipset file (e.g. asr, quectel) or _custom. Use at_knowledge_chipsets to see available platforms. |
| at_knowledge_listA | List all commands in the knowledge base, optionally filtered by source. Shows key, name, and expected response summary. |
| at_knowledge_statsA | Show knowledge base statistics: total commands, per-source YAML file breakdown, source distribution. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/zeng-andrew/at_bridge'
If you have feedback or need assistance with the MCP directory API, please join our Discord server