Ingest data from any MCP server

We’d love to know how you’d like this to work! Please drop a comment in this thread describing your ideal UIUX. Here’s how we are approaching this — feedback?

Step-by-Step: Adding a Storytell Data Ingest Connection via MCP

1. Connection Name

• Prompt: “Name this connection (optional):”

• Purpose: Makes it easier for users to distinguish multiple integrations (e.g., “Jira Prod”, “Internal GitHub”).

2. MCP Server Endpoint (URL)

• Prompt: “Enter the MCP server endpoint URL:”

• Purpose: This is where your MCP client will reach out to fetch data.

  • Example: https://jira.mycompany.com/mcp or an internal IP/FQDN if behind VPN.

3. Authentication Method

• Prompt: “How should we authenticate?”

  • Choices: API Key, OAuth, Username & Password, Service Account, etc.

• Purpose: Different MCP servers may support different authentication mechanisms.

  • If API Key: Ask for the key.

  • If OAuth: Start OAuth flow (redirect, pop-up, or device code flow).

  • If Username & Password: Ask for both.

  • If Service Account: Upload credentials file or JSON.

4. Data Source Type: (Optional but Useful)

• Prompt: “What kind of data source is this MCP server exposing?”

  • Choices: Jira, GitHub, ServiceNow, Custom, etc.

• Purpose: Helps pre-configure or customize field mapping, UX, icons, etc.

5. Data Scope/Filters (Optional, Advanced)

• Prompt: “Do you want to limit the data scope?”

  • Options: Projects, repositories, date ranges, entity types.

• Purpose: For big orgs, users might not want to ingest everything—let them pick.

6. Test Connection

• Button: “Test Connection”

• Purpose:

  • Attempt to connect with provided info.

  • Show error if fails (bad URL, bad auth, etc.).

  • Success? Show some preview data or “Connection successful!”

7. Confirm/Save

• Prompt: “Save connection” (on success)

• Action: Store credentials securely, and schedule/trigger the initial sync.

Example Form UI

1. Connection Name: [___________]

2. MCP Server URL: [https://________]

3. Authentication:

   • API Key [ ] OAuth [ ] Username & Password [ ] Service Account

   • Show fields based on selection

4. Source Type: [Dropdown: Jira, GitHub, Custom, etc.]

5. Scope (optional):

   • Projects/repos: [___________]

   • Date range: [Start ___] [End ___]

6. [Test Connection]
   (Show status feedback here)

7. [Save Connection]

What Happens After?

• Once connected, Storytell would:

  1. Use the stored info to fetch and normalize data.

  2. Optionally, allow the user to edit connection later or disconnect.

Summary Table