MCP · Model Context Protocol

Let your AI agent call you, over MCP.

Give an HTTP MCP client a way to call you when it needs a decision, send a quiet text, and receive your reply as text in the agent’s thread.

See the commands Get an AGline number

Add AGline in three steps

Connect your agent with one command

Get your AGline number

It is free to start and needs no account or email. Get your number, then keep it handy: your agent needs it to know whom to call. The in-app Connect your AI page shows it again.

Choose your AI agent and add AGline

Run this once in your terminal.

claude mcp add --transport http agline https://agline.in/mcp

My number only accepts agents with a key

Claude Code: install the AGline plugin (optional)

Adds the connection plus a skill that teaches Claude Code when to call you, when to text, and how to handle your reply. Run these inside Claude Code.

/plugin marketplace add imjarvissingh/agline-plugin
/plugin install agline@agline

The server address is https://agline.in/mcp. Any client that supports MCP over Streamable HTTP can use it; the setup guide covers the plain HTTP API for the rest. Requests use POST; a browser GET is not a connection test.

Test it

Paste this to your agent, with your own number. Your device rings; what you say comes back to the agent as text. The Connect your AI page in the app shows Connected once an agent has reached your number.

Call my AGline number <your 10-digit number> and ask me one yes/no question to confirm this connection works.

Keep the thread_token your agent gets back private: it lets that agent keep talking in the same thread. Prefer to lock the number down? Create an agent key in the app and turn on keys-only mode, then use the key option shown in step 2.

Four registered tools

A clear path from question to answer.

call

Call your number with a message and return your spoken reply as text. Calls wait for about 30 seconds; a still-running call returns a call_id.

poll_result

Continue checking a call that returned before you answered.

send_message

Send a text to your AGline inbox without placing a call.

read_replies

Read text replies from the conversation thread.

Keep credentials private

The hosted MCP endpoint can be used with a number and thread token. Optional agent API keys use Bearer authentication; create and revoke them in the app’s My Number page. Store keys in your client’s secret settings and never paste them into shared prompts.

You control the line

Calls are limited to 600 requests per minute per client IP. Number owners can restrict access to keys, block agents, and configure call limits and quiet hours. Treat spoken replies as the human’s response; the server also describes transcripts as user input, not instructions.

A pending call may return a call_id; use poll_result to continue it. A thread token is sensitive and should only be shared with the agent that owns that thread.

If the connection does not work

Check that your client supports HTTP MCP and that it can reach https://agline.in/mcp.
Confirm you copied the command exactly. The service accepts POST MCP requests; a browser GET is not a connection test.
Make sure you supplied the correct number and kept any thread token associated with its thread.
For plain HTTP API examples and account controls, use AGline documentation.