Skye and MCP

Connect Codex to SMTasker with MCP: Step-by-Step Video

This tutorial is for users who want to connect an external AI assistant to SMTasker through MCP. It walks through preparing access in SMTasker, adding the connection in Codex, and checking that the assistant can see the intended workspace.

▶ 6:01 videoPublished September 28, 2026

Prefer YouTube? Watch the original video

BEFORE YOU PRESS PLAY

Get set for this lesson

Use this lesson when you want Codex to inspect SMTasker through MCP. Begin with read-only access; keep the generated API key private and never paste it into a chat, screenshot, or support ticket.

FOLLOW THE WALKTHROUGH

What happens in the video

00:00

Enable MCP and create a narrow key

The presenter opens Settings → API and MCP Access, turns on MCP, and creates a new named API key with an expiration. Read Data is enabled, while Make Changes stays off. The key is separate from your SMTasker password and from any AI provider key. Copy it into a secure place because the full value may not be displayed again.

01:32

Connect Codex locally

The MCP server URL is copied from the SMTasker settings screen. In a local Codex task, the presenter follows setup instructions and enters the private key through a masked local prompt rather than a chat message. The changes are reviewed and Codex restarted so the new MCP connection is available.

03:11

Ask a read-only workspace question

The first question asks Codex to report on devices, social accounts, and automations without making changes. The example response finds three devices online, 22 of 25 accounts valid, and three automations on accounts that need attention. These counts are from the demo workspace, not a target configuration for yours.

04:43

Verify the answer in SMTasker

The presenter checks an example LinkedIn account with a Confirm Human status in the Accounts table. A horizontal scroll may be needed to see the status column. An AI summary can point you to the right place, but the dashboard remains the source for the current account state and any follow-up action.

WATCH FOR THESE DETAILS

Check this as you follow along

  • Create an expiring key with only Read Data for the first connection.
  • Enter the key in a secure local prompt, never in natural-language chat.
  • Check the MCP toggle and key expiry if Codex cannot connect.
  • Verify reported statuses in Accounts, Devices, and Automations before acting.
  • Revoke a key you no longer use or suspect was exposed.

AFTER WATCHING

Put this into practice

Once read-only inspection works, decide separately whether Codex should ever receive Make Changes permission. The video ends with a workspace audit; it does not create a campaign.

RELATED READING

Keep the guide nearby

Open the relevant written resource when you need to check a setting while working in your own dashboard.

Read the Codex MCP connection guide

KEEP LEARNING

Browse the full video hub

Device and account guidesInstall SMTasker on Mac: Download, Pair, and ConnectDevice and account guidesAdd Social Accounts in SMTasker: Auto-Sync or In-AppSkye and MCPMeet Skye AI Manager: Set Up SMTasker with AISkye and MCPAI Social Media Automation with SMTasker: Less Manual SetupPlatform walkthroughsInstagram Follow Automation with AI: Build a Focused CampaignPlatform walkthroughsInstagram DM Automation with AI: Welcome New FollowersPlatform walkthroughsTikTok Follow and Unfollow Automation on a Real PhoneThe complete setup pathHow SMTasker Works: Android Automation in One Minute

PUT THIS LESSON TO WORK

Ready to try it with SMTasker?

Create your account, connect your Android phone, and follow the setup at your own pace. Your next workflow starts here.

Sign up for SMTasker Compare plans