3DIMLI MCP Server

Enable compatible remote MCP clients to work with your signed-in 3DIMLI account through an OAuth-enabled MCP server for account settings, purchases, downloads, seller store data, and seller product management.

Overview

The Model Context Protocol (MCP) is an open standard that allows AI clients to securely connect to external tools and data sources. The 3DIMLI MCP Server gives compatible MCP clients structured access to your 3DIMLI account so they can help with profile updates, seller workflows, product management, downloads, and related account tasks.

This public MCP server is designed for focused account and seller workflows. It supports profile settings, purchases, downloads, seller store settings, and seller product management through the same server-side rules used across 3DIMLI.

Key capabilities

• Personal profile and billing management
• Purchase history, purchase-detail lookup, and refund note history
• Download listing and download metadata lookup
• Helpdesk documentation search and issue reporting
• Seller store profile, seller billing overview, and seller billing management
• Support-email OTP verification before support-email changes
• Seller product editing, audit replies, scheduling, publishing, and unpublishing

Quick setup

Connect the public 3DIMLI MCP server in your AI client:

Claude Desktop

Add the connector from the Claude Desktop UI:

1. Open Settings -> Connectors.
2. Add the 3DIMLI connector or paste the remote MCP server URL if prompted: https://www.3dimli.com/api/mcp/connector/mcp
3. Complete the OAuth sign-in flow in your browser.
4. Approve the requested access scopes.

note

Anthropic's current docs say Claude Desktop should connect to remote MCP servers through Settings -> Connectors. Remote servers should not be added directly to claude_desktop_config.json.

Claude Code

Run:

claude mcp add --transport http three_dimli_connector https://www.3dimli.com/api/mcp/connector/mcp

Then inside Claude Code:

/mcp

Use the MCP menu to authenticate in your browser and approve the OAuth access request.

Lovable

Add the connector from Lovable's personal connectors UI:

1. Go to Settings -> Connectors -> Personal connectors.
2. Click New MCP server.
3. Enter a clear server name such as 3DIMLI MCP.
4. Set the server URL to: https://www.3dimli.com/api/mcp/connector/mcp
5. Choose OAuth as the authentication method.
6. Continue through the browser-based OAuth approval flow.

After authorization, Lovable can use the connector as a personal MCP server in your workspace.

Cursor

Add the server to your Cursor MCP configuration.

Project-scoped config:

{
  "mcpServers": {
    "three_dimli_connector": {
      "url": "https://www.3dimli.com/api/mcp/connector/mcp"
    }
  }
}

Common locations:

• Project: .cursor/mcp.json
• Global: ~/.cursor/mcp.json

After saving the config, let Cursor connect and complete the OAuth sign-in flow when prompted.

Windsurf

Add the server to your Windsurf MCP configuration.

{
  "mcpServers": {
    "three_dimli_connector": {
      "serverUrl": "https://www.3dimli.com/api/mcp/connector/mcp"
    }
  }
}

Common location:

• ~/.codeium/windsurf/mcp_config.json

After saving the config, let Windsurf open the OAuth flow and approve the requested scopes.

note

Windsurf's docs note that some Enterprise workspaces require MCP to be enabled in admin settings before users can add servers.

More clients

The same public MCP server URL can work in other MCP-capable tools that support remote Streamable HTTP servers and OAuth.

We currently publish step-by-step setup only for clients whose public documentation clearly describes their remote MCP configuration flow. Trae is not listed yet because its current public material discusses MCP support, but does not clearly document a stable remote-server configuration format and file location we can point users to.

Public MCP server endpoints

• Resource URL: https://www.3dimli.com/api/mcp/connector/mcp
• OAuth authorization page: https://www.3dimli.com/mcp/authorize
• OAuth metadata: https://www.3dimli.com/.well-known/oauth-authorization-server
• Protected resource metadata: https://www.3dimli.com/.well-known/oauth-protected-resource/api/mcp/connector/mcp
• Documentation: https://support.3dimli.com/integrations/3dimli-mcp-connector

Authentication

The public MCP server uses OAuth 2.0 authorization code flow with PKCE.

You do not need to manually copy API tokens when using a compatible OAuth-enabled remote MCP client. The client redirects you to 3DIMLI, you sign in, approve the requested scopes, and then reuses the authorized connection for future requests.

Advanced and internal setups

3DIMLI also has a broader account MCP route for advanced manual bearer-token setups and internal workflows, but that is not the narrowed public MCP server surface documented here.

Compatibility notes

The public MCP server is built for general remote MCP clients that support:

• Streamable HTTP transport
• OAuth 2.0 authentication
• Structured MCP tools

Current positioning:

• Suitable for general tool-calling MCP clients
• Suitable for Claude's reviewed connector flow
• Suitable for other compatible MCP clients that can connect to a remote OAuth-protected MCP server
• Not designed as an OpenAI deep-research or company-knowledge MCP surface, because those product surfaces expect read-only search and fetch tools with a different compatibility schema

Included tool surface

Personal account

Tool	Description
get_user_profile	Fetch personal profile, role, and seller linkage
update_user_profile	Update name, theme, newsletter, bio, website, and gender
get_billing_address	Fetch buyer billing address
update_billing_address	Create or update billing address
list_purchases	Payment summaries, seller-grouped items, and refund state
get_purchase_details	Full order details including refund history
get_refund_request_log	Fetch full buyer/seller refund note history for a purchase
list_downloads	Downloadable purchases with filters and metadata
get_download_metadata	Secure download metadata for a purchased item

Support and reporting

Tool	Description
get_help_docs	Search the 3DIMLI helpdesk documentation for guides, setup steps, and policy explanations
report_issue	Submit a bug or crash report to the 3DIMLI team

Seller account

Tool	Description
list_products	List seller product catalog with search and filters
get_product_editor_data	Full product payload for editing
update_product	Modify title, description, pricing, SEO, attributes, and variants
schedule_product	Set product availability windows
publish_product	Publish a product to the store
unpublish_product	Remove a product from the store
get_product_audit	Fetch audit feedback from the 3DIMLI team
reply_to_audit	Respond to audit conversations
send_product_for_review	Submit a product for review
get_store_profile	Fetch seller store branding, name, and description
update_store_profile	Update store metadata and branding
get_seller_billing_overview	Seller subscription status, storage usage, and billing summary
get_seller_billing_address	Fetch seller billing address
update_seller_billing_address	Update seller billing address
send_support_email_otp	Send OTP to verify a new support email
verify_support_email_otp	Verify the OTP code for support email change

Example workflows

Example 1: Update a personal profile

User prompt: "Show my 3DIMLI profile, then update my bio to mention architectural visualization and keep everything else unchanged."

What the client does:

• Calls get_user_profile
• Updates only the requested fields through update_user_profile
• Returns the refreshed profile payload

Example 2: Verify and save a seller support email

User prompt: "Change my store support email to [email protected]. If verification is needed, send the OTP first and ask me for the code."

What the client does:

• Sends the OTP through send_support_email_otp
• Waits for your 6-digit code
• Verifies it with verify_support_email_otp
• Saves the verified email with update_store_profile

Example 3: Update and publish a seller product

User prompt: "Open product 0e51ccb8-d725-4240-a0f1-010e52d5ea1d, update the title and SEO description, then publish it if it is ready."

What the client does:

• Reads the current payload with get_product_editor_data
• Applies metadata changes through update_product
• Publishes with publish_product, or surfaces review blockers if the product still requires review

Example 4: Schedule a release window

User prompt: "Schedule my product to go live next Monday at 9:00 AM Asia/Kolkata and end Friday at 6:00 PM."

What the client does:

• Validates the request against the seller scheduling rules
• Saves the window with schedule_product
• Re-reads the product payload if needed to confirm the scheduled state

Safety model

The public MCP server intentionally follows the same server-side rules used by the 3DIMLI dashboard.

Examples:

• Username and profile-photo changes are not exposed through this public MCP server
• Support email changes require OTP verification when needed
• Product edits still use the existing product validation and review logic
• Upload-managed assets remain outside MCP and continue to use the dashboard upload pipeline

Troubleshooting

If you run into connection or auth issues:

1. Reconnect the MCP server and complete the OAuth approval flow again.
2. Confirm your client supports remote MCP over Streamable HTTP.
3. Verify you are using the public MCP server URL: https://www.3dimli.com/api/mcp/connector/mcp
4. If the connected account should have seller tools, make sure the account has an active linked seller profile.
5. If a seller action is missing, check that the connected account has an active seller profile and reconnect if your approved scopes have changed.

FAQ

Does 3DIMLI provide an MCP server?

Yes. 3DIMLI provides an OAuth-enabled MCP server that remote MCP clients can use with your 3DIMLI account for profile settings, purchases, downloads, helpdesk search, issue reporting, seller store settings, seller billing, and seller product management.

How do I authenticate the 3DIMLI MCP server?

The public MCP server uses OAuth 2.0 authorization code flow with PKCE. You sign in to your 3DIMLI account, approve the requested scopes, and a compatible MCP client uses that authorized connection for future requests.

Can an MCP client change store support email through the MCP server?

Yes, but only through the proper OTP flow. A compatible client can send the support-email OTP, ask you for the verification code, verify it, and then save the new support email.

Support and policies

• Privacy Policy: https://www.3dimli.com/privacy-policy
• Data Processing Addendum: https://www.3dimli.com/data-processing-addendum
• Terms of Services: https://www.3dimli.com/terms-of-services
• Support email: [email protected]
• Discord: https://discord.gg/d48csuWe46