Connect PromtPress to Claude or Cursor and ask for advertising in plain words. The assistant picks a format, runs the forecast and puts the campaign together. Launching happens either on your confirmation, or within the amount you allowed it to spend.
MCP is a way to give your AI assistant access to a service. Not an app, not an extension: you paste one address into its settings, and the assistant becomes able to work with your advertising.
This is an address, not a password: without email sign-in it opens nothing.
This is not a setting you might flip by accident. Tools for topping up a balance, changing payout details or moving money anywhere simply do not exist in this server — not as an option, not at all. Top-ups happen in the browser, by you; the assistant can only hand you a payment link.
The worst a fully compromised assistant can do is spend what is already on the balance, within your limit, on campaigns you can stop with one click.
Even if the assistant fires ten launches at once, the money is charged and the limit is checked in the same moment. The total can never exceed what you allowed.
The channel, format and budget you saw are bound to the confirmation link. Change the budget afterwards and the link stops working — you have to be shown the new numbers and asked again.
On a new account the allowance is zero, whatever sits on the balance. First you see what the assistant proposes, and only then decide how much independence it gets.
This caps money, not the number of campaigns, and it is not a pricing tier. Run as many campaigns as you like — everything is bounded by the sum. Above the limit the assistant launches nothing: it sends you a link showing the channel, the format and the budget, you press confirm — and only then money moves.
it may spend on its own per campaign launch
it may spend on its own per day, across all campaigns
comes to you as a confirmation link, valid for 15 minutes
It all lives in one place: Dashboard → Profile → How much the assistant spends
on its own. The same card has a “Freeze spending” switch: the assistant keeps
showing statistics but cannot spend a cent. On and off instantly.
Open settings →
Separately: three permissions are granted independently — view (balance and statistics), prepare (forecasts and drafts), spend. You can grant the first two and never grant the third: the assistant will calculate and propose, and you will launch.
The rest read state or prepare a draft. Forecasting and assembling campaigns is unlimited and costs nothing.
get_account balance, limits and what is left of themlist_formats placement formats and price rangesanalyze_channel break down a Telegram channel before buyinglist_campaigns your campaignsget_campaign one campaign in detailget_stats statistics for a periodget_ledger balance movementsget_topup_link send you a top-up link — you pay, in the browserinvite start registration on your email — you finish it via the linkestimate forecast the result for a budgetcreate_campaign draft a campaignupdate_campaign edit the draftsubmit_campaign launch — the only tool that spendsset_budget change the daily budgetpause_campaign pauseresume_campaign resumeNothing to copy, and nothing to look for in the dashboard — there is no key there. You paste one address into your assistant's settings. On first use it opens a PromtPress page itself: you see exactly what you are allowing, enter your account email and follow the link from the message. Much like “Sign in with Google” elsewhere.
Customize → Connectors → “+” → Add custom connector, paste the address, press Add. Leave the OAuth fields under “Advanced settings” empty — our server registers the assistant on its own.
On team plans the owner adds the connector (Organization settings → Connectors → Add → Custom → Web) and everyone else then presses Connect. The free plan allows one custom connector. You cannot add one from a phone — only use one already added.
First go to Settings → Security and login and turn on Developer mode. Then open chatgpt.com/plugins → “+” and create an app with the address. It lands in Drafts; in a chat you pick it from Plus → Developer mode.
Web only, and on Plus, Pro, Business, Enterprise or Education — not on the free plan. In work accounts an admin enables the mode first.
Add to ~/.cursor/mcp.json (or .cursor/mcp.json
in the project):
{
"mcpServers": {
"promtpress": {
"url": "https://mcp.promtpress.com/mcp"
}
}
}
No type field is needed for a remote server.
The server shows up as “Needs login” — click it and the sign-in opens.
The address is the same everywhere; only the field name differs — and that is exactly where people get stuck.
claude mcp add --transport http promtpress https://mcp.promtpress.com/mcp
Then run /mcp in the session and sign in through the browser.
If you edit .mcp.json by hand, you must include
"type": "http": without it the entry is read as a local server
and silently does nothing.
{
"servers": {
"promtpress": {
"type": "http",
"url": "https://mcp.promtpress.com/mcp"
}
}
}
File .vscode/mcp.json in the project, or .mcp.json.
The top-level key here is servers — not mcpServers
like almost everywhere else.
{
"mcpServers": {
"promtpress": {
"serverUrl": "https://mcp.promtpress.com/mcp"
}
}
}
File ~/.codeium/windsurf/mcp_config.json. The field is
serverUrl, not url.
{
"context_servers": {
"promtpress": {
"url": "https://mcp.promtpress.com/mcp"
}
}
}
Or through the UI: Settings → AI → MCP Servers → Add Server →
Add Remote Server. Do not add an Authorization header — with
one present the email sign-in never starts.
{
"mcpServers": {
"promtpress": {
"httpUrl": "https://mcp.promtpress.com/mcp"
}
}
}
httpUrl is what selects the right transport here. Plain
url means something else and will fail. Sign in with
/mcp auth promtpress.
Custom apps for Spark → Add a custom app → the address. No credentials to enter.
Google's limits, not ours: US only, personal Google account (not work or school), 18+, English interface.
codex mcp login promtpress
The server lives in ~/.codex/config.toml. The
codex mcp add command has no flag for a URL — a remote server is
added by editing the file.
We are listed in the Smithery catalogue: smithery.ai/servers/cigamegadrive/PromtPress-Ads. Press Add to toolbox there and the sign-in opens by itself. Useful when your assistant takes servers from Smithery rather than from a config file — the address and the sign-in are the same as everywhere else.
Raycast, LM Studio, Goose, Amp, LibreChat,
Open WebUI (admin), Kiro, Copilot Studio, Perplexity
(Pro and Max): add a remote server of type http with our address
and the sign-in opens by itself.
JetBrains AI Assistant, Roo Code, Copilot on github.com
and Google AI Studio cannot do email sign-in yet — they only accept a
pre-issued key, and we do not have one. A workaround exists
(mcp-remote), but we do not recommend it: an extra layer on the
path to money.
n8n and Make ask for a client id and secret up front — write to us and we will issue them separately.
The assistant opens a PromtPress page itself. Enter the email your account is registered to and follow the link from the message. No account yet — it will be created on that same email, and you top up the balance later in the browser.
No email arrived — the screen has a “Send again” button, and if it stays quiet, write to hello@promtpress.com.
No. The limit is checked and charged in the same moment the campaign launches, so firing requests in parallel gets nowhere. Anything above the limit arrives as a confirmation link and lives 15 minutes.
No. No such tools exist. Top-ups and anything touching payment data happen only in the browser, by you.
They could spend what is left on the balance, within your limit — and nothing beyond: no withdrawal, no top-up, no changing details. Access is revoked in the dashboard in one click: Profile → AI assistants → Revoke. Campaigns stop, the money stays on the balance.
Only if you granted it the view permission. The three permissions — view, prepare drafts, spend — are separate, and any of them can be withheld.
The assistant receives exactly the data it requests on your behalf: balance, campaigns, statistics. That goes to the service you are using — Claude, Cursor — and is handled under its rules. Payment data is never passed: it exists in no command.
Ask the assistant for a top-up link — it will send one into the chat, and you pay in the browser by card or by invoice for a company. The assistant never touches the payment: it has no command that moves money.
The campaign pauses instead of going negative: the assistant cannot spend on credit. You get an email, and on its next turn the assistant will say the balance is empty and send a top-up link. After the top-up the campaign resumes from where it stopped — nothing to rebuild.
To stop one campaign — tell the assistant to pause it, or press pause in the dashboard. To forbid spending but keep statistics — “Freeze spending” in your profile. To disconnect entirely — “Revoke”: the assistant loses access immediately and the money stays on the balance.
Gambling, betting, adult content and anything requiring a licence we cannot verify. Such campaigns are rejected before they reach a source.
Connecting and the assistant itself are free; there is no separate MCP fee. You pay for placements only, at the same prices as in the dashboard: see formats and prices →. Note that connecting third-party MCP servers is a paid-plan feature of Claude and other assistants — their terms, not ours.
That is how the advertising balance works: media is bought in dollars and limits are counted in them. You pay in your own currency: the amount is converted at the central-bank rate for your payment method on the day of payment. The rate and its date are shown at checkout.
Forecasts, drafts and approvals cost nothing. Money moves only when you confirm the launch.
Create an account Ask a question