StoreSign in

SHIPPED · v1.3.0

Connect Your AI Tools with AI Access

New

  • Connect your AI tools to 1MarketingTool from one page. The onemarketingtool MCP server moved out of a Settings sub-tab into its own AI Access page under System.

  • Let agents publish — after a human approves. AI agents can now list your channels, publish library pieces, schedule them for later, list scheduled posts, and cancel them, through a new publishing tool group.

  • Post to X as a different account than the app owner. The X channel gained a Connect button: approve the app in a browser signed in to the account you want to post as — a brand handle instead of the developer account that owns the keys — and the tokens are stored on this device. Pasting an owner access token still works when you only post as the app owner.

Improved

  • X channel setup matches the current X console. Fields are renamed to Consumer Key / Consumer Key Secret with one-line hints telling them apart from the OAuth 2.0 Client ID the console also shows, the access-token pair is optional when you use Connect, and the setup guide walks through console.x.com — including where pay-per-use credits actually live.

  • Every agent call is logged by name. MCP calls land in Logs → AI and the AI Access activity feed under the tool that ran, and calls refused by your permission switches show as blocked rather than failed.

  • The local bridge agents talk to is locked to your tools. It now requires a per-launch token and refuses requests that arrive from a web page, so the publishing tools can't be driven by anything except the clients you connected.

  • AI setup links go to the right place. Onboarding, capability setup, and Settings all route to the AI Access page instead of the retired MCP tab.

Fixed

  • Clients pointing at an old install reconnect themselves. On launch, saved MCP entries that reference a server script which no longer exists are repointed to the current one — updating the app no longer leaves connected tools silently dead.

  • X billing errors name the real problem. An out-of-credits response now identifies the developer account X billed and sends you to console.x.com → Billing → Credits instead of the Event subscriptions page — and tells you to check the Development-to-Production app switch when the balance already looks fine.

  • AI Access Setup tab with the 1MarketingTool MCP server running, connected-tools and 24-hour call counts, and Connect or Disconnect buttons for Claude Code, Codex CLI, Gemini CLI, OpenCode, Cursor and Windsurf
    AI Access Setup tab with the 1MarketingTool MCP server running, connected-tools and 24-hour call counts, and Connect or Disconnect buttons for Claude Code, Codex CLI, Gemini CLI, OpenCode, Cursor and Windsurf
  • AI Access Tools & permissions tab with switches for the Rank & keywords, Content, Video, Website capture and Publishing tool groups and the Approved content only publishing guardrail
    AI Access Tools & permissions tab with switches for the Rank & keywords, Content, Video, Website capture and Publishing tool groups and the Approved content only publishing guardrail
  • Content Library with two draft campaign pieces selected and the bulk Approve (2) button that clears them for publishing by AI agents
    Content Library with two draft campaign pieces selected and the bulk Approve (2) button that clears them for publishing by AI agents
  • A coding agent terminal where the user asks the agent to use the 1MarketingTool MCP server to publish the most recent campaign
    A coding agent terminal where the user asks the agent to use the 1MarketingTool MCP server to publish the most recent campaign
  • The resulting Bluesky post, published by an AI agent through the 1MarketingTool MCP publishing tools
    The resulting Bluesky post, published by an AI agent through the 1MarketingTool MCP publishing tools