Nexus Share Nexus Share

🤖 Nexus Share MCP Server

Connect Your AI Assistant to Nexus Share
Environment: Production Generated: 2026-11-18 18:40:49 UTC

📖 What is the Nexus Share MCP Server?

The Nexus Share MCP (Model Context Protocol) Server allows AI assistants like Claude, ChatGPT, and others to directly interact with your Nexus Share account. This means you can:

  • ✅ Create and schedule social media posts through conversation
  • ✅ Manage your connected social networks
  • ✅ Generate AI images for your posts
  • ✅ Cross-post blogs to Medium, Dev.to, Hashnode
  • ✅ Create and manage recurring posts
  • ✅ Check post analytics and performance
  • ✅ Enhance content with AI
  • ✅ Get intelligent scheduling recommendations
  • ✅ Analyze and apply your writing style

Two Ways to Connect

🌐 Remote MCP Server

Cloud-hosted HTTP server using Streamable HTTP transport. Best for personal use with IDEs like Kiro, VS Code, Cursor, and Claude Desktop. No persistent connections needed - works perfectly with serverless Lambda.
🤖 AgentCore Gateway (AWS Bedrock)

AWS Bedrock-specific gateway for production AI agents. Best for enterprise applications and AWS Bedrock agent integration.
💻 Local MCP Server

Runs on your computer. Best for development, testing, and offline use.

All options provide access to the same 39 MCP tools covering post management, social networks, AI image generation, blog cross-posting, recurring posts, AI agent, analytics, and writing style.

🌐 Remote MCP Server (IDE Integration)

The Remote MCP Server is a cloud-hosted HTTP server using the Streamable HTTP transport protocol. Simple authentication with just your username and password!

✨ Key Features

  • No local installation - works from any device
  • Simple authentication (username + password)
  • Standard MCP Streamable HTTP protocol
  • Works with Kiro, VS Code, Cursor, Claude Desktop
  • AWS-managed infrastructure with auto-scaling
  • Built-in monitoring via CloudWatch and X-Ray
  • Stateless operation - perfect for serverless
Best for: IDE integration, accessing from multiple devices, no local setup needed

📋 Your Remote MCP Server Information

Server URL:
https://mcp-remote.nexus-share.com
Server Domain:
MCP_REMOTE_nexus-share.com

🔧 IDE Setup (Remote MCP)

The remote server uses simple JWT authentication with your Nexus Share credentials, or Personal Access Tokens (recommended) for a setup-once experience.

Prerequisites

  • A Personal Access Token (recommended) — create one from Admin → API Tokens in Nexus Share
  • Or: Your Nexus Share username and password (for Cognito JWT auth)
  • IDE with remote MCP support (Kiro, Claude Desktop, VS Code, Cursor)

Kiro

1. Get your authentication token

# Set your credentials (use single quotes to avoid shell expansion) NEXUS_USER='your-email@example.com' NEXUS_PASSWORD='your-password' AWS_REGION='eu-central-1' CLIENT_ID='your-client-id' # Authenticate with Cognito curl -X POST https://cognito-idp.${AWS_REGION}.amazonaws.com/ \ -H "Content-Type: application/x-amz-json-1.1" \ -H "X-Amz-Target: AWSCognitoIdentityProviderService.InitiateAuth" \ -d "{ \"AuthFlow\": \"USER_PASSWORD_AUTH\", \"ClientId\": \"${CLIENT_ID}\", \"AuthParameters\": { \"USERNAME\": \"${NEXUS_USER}\", \"PASSWORD\": \"${NEXUS_PASSWORD}\" } }" | jq -r '.AuthenticationResult.IdToken'
💡 Password with Special Characters: Use single quotes around your password to prevent shell interpretation of special characters like !, $, or \

2. Configure Kiro with the remote server:

{ "mcpServers": { "nexus-share-remote": { "type": "streamableHttp", "url": "https://mcp-remote.nexus-share.com", "headers": { "Authorization": "Bearer YOUR_ID_TOKEN_HERE" } } } }

3. Reload Kiro

⚠️ Token Expiration: Cognito ID tokens expire after 1 hour. You'll need to refresh the token regularly. For a simpler experience, use the Local MCP Server which handles authentication automatically.
✅ Recommended: Personal Access Tokens (PATs)

Instead of using short-lived Cognito tokens, you can use a Personal Access Token which is valid for 1 year and doesn't require token refresh. Create a PAT from the Admin → API Tokens tab in Nexus Share.

Configuration with PAT:
{ "mcpServers": { "nexus-share-remote": { "type": "streamableHttp", "url": "https://mcp-remote.nexus-share.com/mcp", "headers": { "Authorization": "Bearer nxs_pat_your_token_here" } } } }
💡 PAT Advantages over JWT:
  • Valid for 1 year (no hourly refresh needed)
  • Individually revocable without affecting your session
  • Create separate tokens per integration (IDE, CI/CD, scripts)
  • No need to expose your password in configuration
💡 Transport Protocol: The Remote MCP Server uses Streamable HTTP (MCP spec 2025-03-26), not SSE. This is a stateless HTTP POST-based protocol that works perfectly with AWS Lambda.

📚 More help: Kiro Remote MCP Guide

Claude Desktop & Other IDEs

Similar configuration applies to other IDEs with remote MCP support. You'll need:

  • Streamable HTTP transport with the server URL
  • Authorization header with your Personal Access Token (recommended) or Cognito ID token

📚 More help: MCP Streamable HTTP Transport Documentation

🏗️ Architecture

┌─────────────────┐ │ IDE (Kiro, etc) │ └────────┬────────┘ │ HTTPS (Streamable HTTP) ┌────────▼────────────────┐ │ Remote MCP Server │ │ (Lambda + API Gateway) │ └────────┬────────────────┘ │ API Calls ┌────────▼────────────────┐ │ Nexus Share APIs │ │ (REST + GraphQL) │ └─────────────────────────┘

🤖 AgentCore Gateway (AWS Bedrock)

The AgentCore Gateway is specifically designed for AWS Bedrock AI agents. This is NOT for IDE integration - use the Remote MCP Server above for that.

✨ Key Features

  • AWS Bedrock-specific protocol
  • Enterprise security (IAM, audit logging)
  • Multi-agent support
  • 99.99% availability SLA
Best for: AWS Bedrock agents, enterprise AI applications, production automation

📋 Your Gateway Information

Gateway URL:
https://mcp.nexus-share.com
Gateway Domain:
MCP_AGENTCORE_nexus-share.com
Gateway ID:
nexus-share-gateway-prod-jwxtauqnzb

🤖 AWS Bedrock Agent Setup

1. Create or open your AWS Bedrock Agent

In the AWS Console, navigate to Amazon Bedrock → Agents

2. Add the AgentCore Gateway as an action group

  • In your agent configuration, go to "Action groups"
  • Click "Add action group"
  • Select "Use AgentCore Gateway"
  • Enter the Gateway ID shown above

3. Configure permissions

Ensure your Bedrock agent has permission to invoke the gateway. The agent's execution role needs:

{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": "bedrock:InvokeAgentCoreGateway", "Resource": "arn:aws:bedrock:REGION:ACCOUNT:gateway/nexus-share-gateway-prod-jwxtauqnzb" } ] }

📚 More help: AWS Bedrock Agents Documentation

🏗️ Architecture

┌─────────────────┐ │ Bedrock Agent │ └────────┬────────┘ │ Bedrock Protocol ┌────────▼────────────────┐ │ AgentCore Gateway │ │ (Gateway ID above) │ └────────┬────────────────┘ │ Invoke Lambda ┌────────▼────────────────┐ │ Lambda Tool Handler │ └────────┬────────────────┘ │ API Calls ┌────────▼────────────────┐ │ Nexus Share APIs │ │ (REST + GraphQL) │ └─────────────────────────┘

💻 Local MCP Server Setup

The Local MCP Server runs on your computer and integrates with AI assistants in your IDE.

✨ Key Features

  • Native IDE integration (VS Code, Cursor, Claude Desktop)
  • Low latency (~10-50ms)
  • Free to run (no AWS costs)
  • Simple 5-minute setup
  • Perfect for personal use and development
Best for: Personal use, local development, IDE integration, testing, cost-sensitive scenarios

📥 Download

Coming Soon: Pre-built packages will be available for download. For now, please contact support@nexus-share.com for access to the local MCP server.

⚙️ Configuration

Prerequisites

  • Node.js 18 or higher
  • Your Nexus Share account credentials (email and password)
  • One of: Claude Desktop, VS Code, or Cursor

🖥️ Claude Desktop Setup

1. Find the configuration file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
  • Linux: ~/.config/Claude/claude_desktop_config.json

2. Add this configuration:

{ "mcpServers": { "nexus-share": { "command": "node", "args": [ "/path/to/nexus-share-mcp-server/dist/index.js" ], "env": { "NEXUS_USERNAME": "your-email@example.com", "NEXUS_PASSWORD": "your-password" } } } }

3. Restart Claude Desktop

4. Test it: Ask Claude "What Nexus Share tools do you have access to?"

💡 Note: By default, the server connects to the sandbox environment. If you need to connect to production or beta, add these environment variables:
NEXUS_API_URL: "https://nexus-share.com/api" NEXUS_GRAPHQL_URL: "https://api.nexus-share.com/graphql"

📚 More help: Claude Desktop MCP Setup Guide

🔧 VS Code / Cursor Setup

1. Install the MCP extension (if using VS Code) or use Cursor's built-in MCP support

2. Add to your workspace settings (.vscode/settings.json or Cursor settings):

{ "mcp.servers": { "nexus-share": { "command": "node", "args": [ "/path/to/nexus-share-mcp-server/dist/index.js" ], "env": { "NEXUS_USERNAME": "your-email@example.com", "NEXUS_PASSWORD": "your-password" } } } }

3. Reload your IDE

📚 More help:

🤖 Kiro Setup

1. Open Kiro MCP Configuration

In Kiro, open the command palette and search for "MCP" or navigate to Settings → MCP Configuration

2. Add the Nexus Share MCP server:

{ "mcpServers": { "nexus-share": { "command": "node", "args": [ "/path/to/nexus-share-mcp-server/dist/index.js" ], "env": { "NEXUS_USERNAME": "your-email@example.com", "NEXUS_PASSWORD": "your-password" } } } }

3. Reload Kiro

4. Test it: Ask Kiro "What Nexus Share tools do you have access to?"

📚 More help: Kiro MCP Configuration Guide

🔒 Security Best Practices

  • Never commit configuration files with credentials to version control
  • Use environment-specific accounts (separate dev/prod)
  • Consider using environment variables instead of hardcoded credentials
  • Rotate passwords regularly

🐛 Troubleshooting

Server not appearing in IDE
  • Verify the path to dist/index.js is absolute
  • Check that Node.js 18+ is installed: node --version
  • Restart your IDE completely
  • Check IDE logs for MCP errors
Authentication fails
  • Verify your username and password are correct
  • Check that you're using the correct API URLs for your environment
  • Ensure your account has API access enabled
Tools not working
  • Verify API URLs match your environment (sandbox/beta/production)
  • Check that your account has necessary permissions
  • Ensure feature flags are enabled for beta features

🛠️ Available MCP Tools

The MCP server exposes 39 tools across 10 categories:

Post Management (6 tools)

create_post
Create a new social media post (draft, scheduled, or publish immediately)
Parameters: content, platforms, scheduledFor?, scheduledIn? (e.g. "10m", "2h", "1d"), title?, tags?, publishImmediately?
list_posts
List posts with filtering and pagination
Parameters: limit?, nextToken?, status?, platform?, fromDate?, toDate?
get_post
Get a specific post by ID (full details including media, threading, published URLs)
Parameters: postId
update_post
Update post content, schedule, or target platforms
Parameters: postId, content?, scheduledFor?, scheduledIn? (e.g. "10m", "2h", "1d"), platforms?, title?, tags?
delete_post
Delete or cancel a post
Parameters: postId
publish_post
Publish a post immediately to all target platforms
Parameters: postId, idempotencyKey?

Convenience Tools (5 tools)

get_recent_posts
Get your most recent posts (shortcut for list_posts)
Parameters: count? (default: 5, max: 20), status?
search_posts
Search your posts by content text
Parameters: query, limit? (default: 10)
duplicate_post
Duplicate an existing post with optional changes (different platforms, tweaked content, new schedule)
Parameters: postId, content?, platforms?, title?, scheduledFor?, scheduledIn?
repost
Republish a previously published post (optionally to different networks or at a later time)
Parameters: postId, platforms?, content?, scheduledFor?, scheduledIn?
bulk_create_posts
Create multiple posts at once (content plans, scheduling a week of posts)
Parameters: posts[] (each with content, platforms, title?, scheduledFor?, scheduledIn?, tags?)

Social Network Management (4 tools)

list_network_connections
View all connected social network accounts
Parameters: none
get_network_connection
Get details about a specific network connection
Parameters: network (X, LINKEDIN, BLUESKY, THREADS, MASTODON, SLACK)
generate_oauth_url
Generate OAuth URL for connecting a new social network
Parameters: network, codeChallenge
disconnect_network
Disconnect a social network account
Parameters: network

User & Subscription (3 tools)

get_user_profile
Get current user profile information
Parameters: none
get_user_statistics
Get user usage statistics (posts, AI usage)
Parameters: none
get_subscription
Get current subscription details (plan, tier, billing)
Parameters: none

AI Content (2 tools)

enhance_text_with_ai
AI-powered content enhancement for better engagement
Parameters: text, targetPlatforms?, tone?, length?
generate_intelligent_schedule
AI-based optimal scheduling recommendations
Parameters: posts, timeRange, flexibility

AI Image Generation (2 tools)

generate_ai_image
Generate up to 3 AI images for a post using Amazon Bedrock
Parameters: postContent, mediaPostId, steeringText?, aspectRatio? (1:1, 16:9, 9:16)
get_image_generation_quota
Check remaining daily/monthly image generation quota
Parameters: none

Blog Cross-Posting (4 tools)

fetch_blog_content
Fetch and parse blog content from a URL (title, body, images, metadata)
Parameters: url
cross_post_blog
Cross-post to Medium, Dev.to, Hashnode, Community AWS
Parameters: blogUrl, title, body, targetPlatforms, tags?
get_blog_credentials
List connected blog platforms and credential status
Parameters: none
get_cross_post_history
Get history of blog cross-posts
Parameters: limit?, nextToken?

Recurring Posts (5 tools)

create_recurring_post
Create a post that repeats on schedule (daily, weekly, monthly, yearly)
Parameters: title, content, targetNetworks, frequency, interval, startDate, daysOfWeek?, endDate?, maxOccurrences?
list_recurring_posts
List all recurring posts with optional filters
Parameters: status?, frequency?
pause_recurring_post
Pause a recurring post
Parameters: id
resume_recurring_post
Resume a paused recurring post
Parameters: id
delete_recurring_post
Delete a recurring post
Parameters: id

AI Agent (4 tools)

trigger_ai_agent
Trigger the AI agent to analyze posts and propose new content ideas
Parameters: none
list_ai_proposals
List AI-proposed posts waiting for review
Parameters: none
accept_ai_proposal
Accept an AI-proposed post (creates as draft or schedules it)
Parameters: proposalId
reject_ai_proposal
Reject an AI-proposed post
Parameters: proposalId

Analytics & Insights (3 tools)

get_post_metrics
Get performance metrics for published posts (likes, shares, impressions)
Parameters: postId, networks
get_shortlink_statistics
Get click analytics for shortened URLs (geographic, device, referrer)
Parameters: shortCode
preview_post_splitting
Preview how content will be split/threaded across networks
Parameters: content, targetNetworks

Writing Style (2 tools)

analyze_writing_style
AI-analyze your writing style from past posts
Parameters: none
get_writing_style
Get your current writing style settings (tone, voice, instructions)
Parameters: none

💬 Usage Examples

Once configured, you can interact with Nexus Share through natural conversation with your AI assistant:

Create a Post

You: "Create a LinkedIn post about the benefits of automation"

AI: Uses the create_post tool to create your post

Schedule Multiple Posts

You: "Schedule 3 posts about AI trends for next week on X and LinkedIn"

AI: Uses generate_intelligent_schedule and create_post tools

Check Analytics

You: "Show me the performance of my last 5 posts"

AI: Uses list_posts and get_post_metrics tools

Enhance Content

You: "Make this more professional: 'We launched a thing'"

AI: Uses enhance_text_with_ai tool to improve your content

📚 Need More Help?

Use the feedback option in the Nexus Share app to get support or ask questions about MCP server setup.