Connect YouScaleIt to the tools you already use
Imagine you have planned your content for the week, and now you want that same information in a report or in the AI assistant you use every day. You shouldn’t have to copy each post by hand.
These docs explain how to connect to YouScaleIt, read your posts, and work with your content from another tool.
Choose where to start
There are two ways to connect. You don’t need both.
| What you want to do | Where to start |
|---|---|
| Read your posts from a script, server, or automation | API keys, then your first API request |
| Let an AI assistant work with your YouScaleIt account | Connect through MCP |
| Find parameters and response details | API read endpoints or MCP tools |
| Understand why a request failed | Troubleshooting |
API or MCP: what is the difference?
With the API, your code sends an HTTP request to a specific endpoint. You choose the parameters and decide what to do with the response. This is useful when you want a repeatable workflow, such as reading your calendar every Monday for a weekly report.
With MCP, an AI assistant discovers the tools YouScaleIt provides and calls them for you. You can ask it to show your scheduled posts instead of writing that request yourself.
There is an important difference between MCP connections, too:
- API-key connections provide the scheduled-post reading tool.
- OAuth connections, when available, can use additional tools for drafts, publishing, scheduling, auto-comments, and reposts, depending on the permissions you approve.
A connected assistant does not automatically have permission to do everything. Read the authorization screen before approving access, especially if it includes publishing or scheduling.
Start with a read
For your first connection, read something you can check in the dashboard. Your scheduled posts for a particular month are a good starting point.
Once that works, you can build a larger workflow. It is much easier to spot a wrong account, missing permission, or date misunderstanding before an automation starts making changes.
Keep your credentials out of the conversation
Your API key belongs in your server’s secret storage or your MCP client’s secure header settings. It does not belong in a prompt, a screenshot, or public code.
The docs explain how to create and use keys. They never need your actual key.
