Jon Wu

Commented on Share Your Feedback on Improving the Agent Buildin...·Posted inAnnouncements

Booked and submitted as well. Looking forward to chatting!

Commented on Integrating Asana and Jira with Dust: Best Practic...·Posted inHelp

Remi thanks for taking a look. Would definitely love a native Asana knowledge integration for more complete search, or even a native Asana MCP for personal credentials, but otherwise I figured external MCP was better than nothing for now. Having Asana whitelist the Dust redirect would at least potentially give more functionality or less external dependency without Pipedream for now.

Posted in Feedback·

Jon Wu

Improving BigQuery Queries: Tips for Avoiding SQL Errors

Jules Belveze (Dust) Maxime Cattet I noticed a pattern with my BigQuery query tables I mentioned yesterday where the generated SQL fails a few times due to a lack of understanding of BigQuery syntax or constraints. It'll always figure it out eventually, but a little guidance seems to fix it, so maybe that's something that's easy to fix by default. The screenshot shows how it'll try a few times with mismatched types, or by using an INTERVAL that's not supported with TIMESTAMP_SUB, but if you add a little info to the data description, it seems to get things right enough on one shot. Something like this seems to make it work on the first shot:

When writing queries, carefully note the column data types to ensure comparisons are valid. Consider BigQuery limitations for TIMESTAMP_SUB as WEEK, MONTH, YEAR intervals are not supported.

1 attachment

2Comments

Posted in Feedback·

Jon Wu

Proposal for Specialized Agent Roles in Data Management

It'd be really helpful to have a light role, which can only access specific agents mapped to it. For example, imagine you have specialized jobs like customer service agents who should only be able to talk to specific agents for their job, but otherwise you'd prefer that must data flows throughout the company so you want most data to be in the public company space. Without this narrower role, my understanding is that almost all data would have to move to a private space to prevent some users from seeing things, so that isn't ideal. If you compare to Slack's permission model, this is kind of like having a single or multi-channel guest, but for agents.

2Comments

Commented on Integrating Asana and Jira with Dust: Best Practic...·Posted inHelp

Jon Wu

Moez GHANMI Thanks for sharing. By workflow, are you referring to an external script and process? Did you just extract the data and copy it to files or some other connection that Dust has access to? I did manage to try Asana with MCP via Pipedream (see https://mcp.pipedream.com/app/asana) instead of the official Asana MCP server. It worked well for one scenario I was trying to extract data and create tasks, put into sections, and add custom fields. Search would be possible too, but the RAG via MCP workflow might not be very comprehensive vs something that Dust would index.

Commented on Integrating Asana and Jira with Dust: Best Practic...·Posted inHelp

Jon Wu

I was trying to add Asana's MCP server, but according to https://developers.asana.com/docs/integrating-with-asanas-mcp-server, they need to allowlist the redirect URI. They have a form to fill out to request a redirect URI to be allowlisted for an MCP client, but I'm not sure what to put here. Can somebody from Dust submit this request form?

Commented on Custom Header Authentication for Remote MCP Server...·Posted inFeedback

Jon Wu

I deployed a proxy via Cloudflare Workers to rewrite this, and that did the job

/**
 * Cloudflare Worker to proxy requests to the Statsig MCP server,
 * rewriting the Authorization header to STATSIG-API-KEY.
 *
 * This allows the Statsig MCP server to be added as a remote MCP server to Dust,
 * which only supports adding Bearer tokens for authentication, and not custom headers.
 */
export default {
  async fetch(request) {
    const url = new URL(request.url)
    const targetUrl = `https://api.statsig.com${url.pathname}${url.search}`

    const newHeaders = new Headers(request.headers)

    // Rewrite the Authorization header to STATSIG-API-KEY
    const authHeader = newHeaders.get('Authorization')
    if (authHeader && authHeader.startsWith('Bearer ')) {
      const token = authHeader.substring(7)
      newHeaders.set('STATSIG-API-KEY', token)
      newHeaders.delete('Authorization')
    }

    // Forward the request to the Statsig MCP server
    const proxyRequest = new Request(targetUrl, {
      method: request.method,
      headers: newHeaders,
      body: request.body,
      redirect: 'manual'
    })

    return fetch(proxyRequest)
  }
}

Posted in Feedback·

Jon Wu

Custom Header Authentication for Remote MCP Servers

For remote MCP servers, allowing a custom header for authentication would be helpful. I'm trying to integrate Statsig, but it doesn't accept a standard Bearer token header. https://docs.statsig.com/integrations/mcp/

1Comment

Commented on Troubleshooting Dust and Zapier Slack Message Inte...·Posted inHelp

Jon Wu

I had a similar use case, but for messages sent via a Slack Workflow, and the issue was also that Dust ignored all bot messages. It would be great if certain bots or channels could be allowlisted.

Posted in Feedback·

Jon Wu

Improving Slack Bot Formatting for Code and Images

It'd be nice if Slack bot formatting was a little better. Of course stuff like React code will never work, but it could be wrapped in a code block or omitted. It'd be nice if a table was wrapped in a code block to be aligned at least. I also noticed if you generate an image, it's not shown in Slack at all, but maybe that's a little harder if that needs to be either public for Slack to see it, or if you'd have to upload it as a file into the message. The use case there is to build a graph image to show as a daily report or something like that.

1 attachment

0Comments