Pine Assistant MCP Server
A local MCP server that lets any LLM agent manage Pine AI tasks — negotiate bills, cancel subscriptions, resolve disputes, and make phone calls on your behalf.
Built on the pine-assistant Python SDK.
Installation
pip install pine-mcp-server
Or run directly with uvx (no install needed):
uvx pine-mcp-server
Quick Start
1. Get your Pine AI credentials
You need an access_token and user_id from Pine AI. Either:
- Sign up at 19pine.ai and retrieve your credentials, or
- Use the built-in auth tools (
pine_auth_request_code/pine_auth_verify_code) to authenticate via email.
2. Configure your MCP client
Claude Desktop — edit claude_desktop_config.json:
{
"mcpServers": {
"pine-assistant": {
"command": "uvx",
"args": ["pine-mcp-server"],
"env": {
"PINE_ACCESS_TOKEN": "your-access-token",
"PINE_USER_ID": "your-user-id"
}
}
}
}
Cursor — edit .cursor/mcp.json:
{
"mcpServers": {
"pine-assistant": {
"command": "uvx",
"args": ["pine-mcp-server"],
"env": {
"PINE_ACCESS_TOKEN": "your-access-token",
"PINE_USER_ID": "your-user-id"
}
}
}
}
If you prefer pip install, replace "command": "uvx" with "command": "pine-mcp-server" and remove the "args" field.
3. Use it
Ask your LLM agent something like:
"Use Pine AI to negotiate my Comcast internet bill. My account number is 12345."
The agent will create a session, send your request, and check back for updates.
How It Works
The server follows a "load conversation" model — like refreshing a browser page:
- Create a session —
pine_session_create - Send a message describing the task —
pine_send_message - Wait, then check what Pine replied —
pine_get_history - Start the task when ready —
pine_task_start - Check again for results —
pine_get_history
There is no real-time streaming. The agent periodically loads the conversation history to see updates, similar to refreshing the Pine web app.
Available Tools
Authentication
| Tool | Description |
|---|---|
pine_auth_request_code |
Request a verification code via email |
pine_auth_verify_code |
Verify the code and obtain credentials |
Sessions
| Tool | Description |
|---|---|
pine_session_create |
Create a new Pine session |
pine_session_list |
List sessions with optional filters |
pine_session_get |
Get details about a session |
pine_session_delete |
Delete a session |
pine_session_url |
Get the web URL to view a session |
Conversation
| Tool | Description |
|---|---|
pine_get_history |
Load conversation history (the core "refresh" tool) |
pine_send_message |
Send a text message to Pine |
pine_send_form_response |
Submit a form that Pine sent |
pine_send_auth_confirmation |
Submit an OTP/verification code |
pine_send_location_response |
Submit location coordinates |
pine_send_location_selection |
Submit a location selection |
Tasks
| Tool | Description |
|---|---|
pine_task_start |
Start task execution |
pine_task_stop |
Stop a running task |
Attachments
| Tool | Description |
|---|---|
pine_upload_attachment |
Upload a local file (bill, screenshot, etc.) |
pine_delete_attachment |
Delete an uploaded attachment |
Social & Scheduling
| Tool | Description |
|---|---|
pine_social_share |
Share results on social media to earn credits |
pine_update_call_reminder |
Update a scheduled call reminder |
Environment Variables
| Variable | Required | Description |
|---|---|---|
PINE_ACCESS_TOKEN |
Yes* | Pine AI access token |
PINE_USER_ID |
Yes* | Pine AI user ID |
PINE_BASE_URL |
No | Pine AI backend URL (default: https://www.19pine.ai) |
PINE_DEVICE_ID |
No | Stable device identifier. Recommended when the server runs as a subprocess (Claude Desktop, Cursor) — otherwise a fresh random ID is generated on each launch if ~/.pine/device_id is unwritable. |
* Not required if you authenticate at runtime using the auth tools.
Development
pip install -e ".[dev]"
License
MIT
Metadata
Release files for pine-mcp-server 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pine_mcp_server-0.1.4.tar.gz | 14.4 kB | With provenance | Details for pine_mcp_server-0.1.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pine_mcp_server-0.1.4-py3-none-any.whl | Python 3 | none | any | Details for pine_mcp_server-0.1.4-py3-none-any.whl |
Total release size: 33.9 kB
Release files / pine_mcp_server-0.1.4.tar.gz
| Download URL | pine_mcp_server-0.1.4.tar.gz |
|---|---|
| Size | 14.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
024b25358c380d64ac08ead0fe7787481552c1373e304a0de487aaf02ab38162
|
|
BLAKE2b-256 checksum How to use checksums |
025b2d812b415e074d3d3ff597675500590902ee4806d02f69c995e0f6963fe7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 23, 2026.
Transparency logRelease files / pine_mcp_server-0.1.4-py3-none-any.whl
| Download URL | pine_mcp_server-0.1.4-py3-none-any.whl |
|---|---|
| Size | 19.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
301d459a222572cbb439004c496c49cfb40687641ff0a96a8998bc0a91464f9f
|
|
BLAKE2b-256 checksum How to use checksums |
d3b3d9b047dfda90fa399ab6acc8af3dbf589c45750a3d986a538537eb2406ac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 23, 2026.
Transparency logSecurity for pine-mcp-server 0.1.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pine_mcp_server-0.1.4.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 23, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.