Connect an AI assistant with MCP

Imagine asking your assistant, “What have I scheduled for this month?” and getting the answer from your actual YouScaleIt calendar instead of copying everything into the conversation.

MCP makes that connection possible. It is a protocol that lets an assistant discover tools and call them with structured inputs.

Connection details

You do not need to run a local YouScaleIt MCP process. You do need a client that supports a remote Streamable HTTP server and one of the authentication methods below.

Availability: OAuth and the additional agent tools depend on the deployed website and backend. This guide describes the current implementation, not a verified compatibility result for every assistant. If OAuth is unavailable, an API-key connection provides calendar reading only, where your client supports secure request headers.

Option 1: Sign in with OAuth

Use OAuth when it is available and you want a connection with explicit permissions rather than a shared API key.

1. Open your assistant’s remote MCP or custom connector settings.
2. Add https://youscale.it/mcp as the server URL.
3. Choose OAuth or sign-in authentication. If asked how to register the client, choose Register automatically.
4. Follow the sign-in flow to YouScaleIt.
5. Review the account or workspace and the requested permissions.
6. Allow the connection only if the permissions match what you want that assistant to do.

Signing in is not the same as approving access. You must explicitly allow the connection on the authorization screen.

Read that screen carefully. A request can include permissions to publish and schedule, not just to read posts. The displayed client name is supplied by the client; it is not proof that YouScaleIt has verified its publisher.

Do not enter an API key as an OAuth client ID or secret. Automatic registration uses a public client without a client secret. Client ID Metadata Document (CIMD) registration is not supported by this implementation.

Check the connection with a read

For example:

Show my scheduled posts for October 2026. Include their platforms and statuses. Do not change anything.

Compare the answer with the calendar in YouScaleIt. Check the month, year, and account before using tools that make changes.

A tool appearing in the assistant’s tool list does not mean the connection has permission to run it. A missing permission can require another authorization step.

Option 2: Use an API key

This connection exposes the read-only scheduled-post tool, not the additional OAuth tools.

1. Create an API key.
2. Add https://youscale.it/mcp in your client’s remote server settings.
3. Select request-header authentication, if your client provides it.
4. Store this header in the client’s secure credential settings:

Authorization: Bearer YOUR_API_KEY

Alternatively, if supported by your client, use:

x-youscaleit-api-key: YOUR_API_KEY

Choose one header. Do not send both, and do not use the REST API’s header name here.

The client must send the credential on every request, including initialization and tool discovery. A “No sign-in” option alone does not configure an API key.

If the client shares connector credentials across an organization, users of that connection may be accessing the key owner’s data. Do not treat a shared key as separate authorization for each person.

Never paste the key into a chat message to ask the assistant to connect itself.

Disconnect an assistant

For OAuth, open Connected agents, find the connection, and disconnect it. Your API keys and website sessions are separate and are not changed by that action.

For an API-key connection, remove the connector and revoke its key from API Keys when nothing else needs that key.

Disconnecting does not undo published content or automatically cancel schedules. Review and cancel unwanted future actions separately.

If you are building an MCP client

Use the MCP lifecycle: initialize, send the initialized notification, discover tools, and then call the tools you need. Let an MCP SDK handle protocol negotiation where possible.

Requests use JSON with these headers:

Content-Type: application/json
Accept: application/json, text/event-stream

Send the relevant authentication header as well. The server uses stateless request/response handling with JSON responses. It does not offer a standalone GET event stream or persistent session deletion.

OAuth clients must support automatic dynamic registration, the authorization-code flow with S256 PKCE, and the exact resource URL https://youscale.it/mcp. Let discovery provide the authorization endpoints rather than hard-coding backend routes. OAuth access tokens use the Bearer header; refresh tokens are not credentials for tool calls.

The API-key path is intended for native or server-side clients. Browser requests carrying an Origin from another site are rejected on that path. Do not put a key in browser code or attempt to bypass the Origin check.

Next: Available tools and permissions, or troubleshooting.